Schemas

The lowercase identity-provider namespace.

A provider-owned identifier up to 256 characters long.

The ACL grant kind. Supported values are 'domain', 'group', 'user', and 'anyone'.

The lowercase provider namespace for this ACL grant, such as 'slack'.

The provider-owned opaque identifier for this ACL grant.

The lowercase provider namespace for this member, such as 'slack'.

The provider-owned opaque identifier for this member.

One ACL grant reference from the request body.

The complete set of current members for this ACL grant. Use an empty array when the grant currently has no members. Grants with kind 'anyone' are always normalized to an empty member set.

Identifies an ACL grant for a subject that may read the content. Membership resolution is performed by the provider named in StackInternal.ContentIngestion.Connectors.Models.AccessControlListGrant.Provider.

The observedAt timestamp applied to this ACL grant.

The number of members granted by this request.

The number of members revoked by this request.

The change-set id for granted members, or null when no grants were recorded.

The change-set id for revoked members, or null when no revokes were recorded.

The payload representation family.

The representation version used for this payload.

The archetype name for the payload.

The Dimension Registry schema identifier used to validate StackInternal.ContentIngestion.Connectors.Models.ArchetypeContentEnvelope.Data.

Archetype payload matching the supplied dataSchema.

Commit subject, pull request title, release name, or other primary label for the change artifact.

High-level change classification such as commit, pull request, release, patch, or version bump.

Timestamp describing when the change artifact was created.

Observed external identifier in the source system for the persona that authored, created, or published the change artifact. Resolution to a persona is based on the source value together with this persona reference and happens in the extraction domain.

Current state such as open, merged, closed, published, draft, or prerelease.

Deep link to the change artifact in the source system.

Commit body, pull request description, release notes, or other long-form explanation of the change.

Timestamp describing the latest metadata update for the change artifact.

Reference to the target branch, previous version, or prior state of the change.

Reference to the source branch, head SHA, or new state introduced by the change.

Timestamp describing when the change was merged, landed, or published.

JSON-serialized collection of related issues, tickets, milestones, or other work-tracking links.

JSON-serialized collection of review entries and review comments associated with the change.

JSON-serialized source-specific metadata such as SHA, tag, file stats, merge queue state, or target commitish.

Display name for the container, such as a repository, channel, project, team, or space name.

High-level container classification such as space, repository, board, team, channel, project, room, or service.

Observed external identifiers in the source system for the owners, leads, maintainers, or administrators for the container. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Deep link to the container in the source system.

Purpose, charter, topic, or description that explains what the container is for.

Timestamp describing when the container was created.

Timestamp describing the most recent metadata change to the container.

Visibility or access state such as public, private, internal, shared, or archived.

Reference to a parent organization, team, portfolio, or space when one exists.

JSON-serialized source-specific container metadata such as default branch, topic, moderation settings, or billing linkage.

High-level conversation classification such as direct message, group chat, channel thread, comment thread, or Q&A thread.

Timestamp describing when the conversation began.

Timestamp of the most recent message or activity associated with the conversation.

Observed external identifiers in the source system for the participants involved in the conversation. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Deep link to the chat, thread, or channel in the source system.

Channel name, thread subject, topic, or another human-readable label for the conversation.

Optional synopsis of the discussion to help consumers understand the exchange quickly.

Ordered collection of normalized message archetype instances materialized for the conversation when callers need the usable thread shape.

Number of messages currently known for the conversation when the source exposes that count.

Reference to the workspace, team, channel, space, or project that contains the conversation.

Conversation state such as active, closed, archived, resolved, or locked.

JSON-serialized source-specific conversation metadata such as thread IDs, visibility, or reply counters.

Human-readable name of the document or document-like artifact.

Extracted body text, OCR text, or the normalized textual representation of the document content.

High-level document classification such as page, file, blog post, note, knowledge article, or attachment.

Observed external identifiers in the source system for the people who created or most recently edited the document. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Canonical deep link back to the document in the source system.

Optional source-provided or generated synopsis that helps a reader understand the document quickly.

Timestamp describing when the source document was first created.

Timestamp describing the most recent source-side modification to the document.

Reference to the parent space, repository, drive, folder, channel, or project that contains the document.

MIME type for file-backed content when the source exposes one.

Natural language code or label for the extracted content when it is known.

JSON-serialized collection of labels, categories, or source taxonomies associated with the document.

Lifecycle or publication state such as draft, published, archived, deleted, or current.

Source-specific version number, revision identifier, or current document revision label.

JSON-serialized source-specific metadata that does not cleanly promote to a canonical document property.

The upstream system that produced the content, such as 'github' or 'slack'.

The stable identifier from the upstream system for this content item. The combination of source and sourceId must be unique within the tenant.

The absolute URI of the content item in the upstream system.

The access control entries that define who can view the content.

The source-specific entity type for this content item, such as 'markdown-file' or 'message'.

Standardized archetype envelope used for transport and storage.

The optional absolute URI-shaped container hierarchy for this content item.

Optional root-to-leaf containers with stable IDs and display names. Requires a matching hierarchy URI.

The unique identifier of the stored content version that was created.

The message body or normalized textual content of the utterance.

High-level message classification such as chat, comment, review, reply, Q&A, note, or announcement.

Timestamp describing when the message was first created or submitted.

Observed external identifier in the source system for the persona that authored or sent the message. Resolution to a persona is based on the source value together with this persona reference and happens in the extraction domain.

Deep link to the exact message in the source system.

Optional subject line, heading, or generated snippet for the message.

Timestamp of the latest source-tracked edit to the message.

Reference to the parent conversation when the message belongs to one.

Reference to the immediate parent object such as a work item, document, message, or review object.

Reference to the direct parent message or comment when the source models threaded replies.

Observed external identifiers in the source system for mentioned personas or entities captured from the message. Resolution to a persona or other mentioned identity is based on the source value together with each mention reference and happens in the extraction domain.

JSON-serialized collection of attachments or linked artifacts associated with the message.

JSON-serialized reaction counts or structured reaction metadata captured for the message.

JSON-serialized source-specific message metadata such as subtype, importance, visibility, or line context.

Broad measurement family such as usage, attendance, traffic, queue performance, or SLA.

Reference to the user, team, organization, repository, session, queue, service, or other subject being measured.

Timestamp of the snapshot capture or the representative timestamp for the measured period.

JSON-serialized map of numeric measurements keyed by metric name.

Deep link to the source report or metric record when the source provides one.

Start timestamp for the measured period when the snapshot covers a window of time.

End timestamp for the measured period when the snapshot covers a window of time.

JSON-serialized dimension bag describing slice values such as language, IDE, model, queue, channel, or feature.

Level at which the metrics were aggregated, such as user, team, org, repo, session, or queue.

JSON-serialized source-specific rollup metadata such as sample counts, report IDs, or derived counters.

The registered API-managed source or authorized internal connector source that owns this ACL membership snapshot.

The time this snapshot was observed in the upstream system.

The ACL grants to replace. Each grant is a full replacement of its current member set.

The synthetic ingestion run recorded for this request.

Per-grant grant and revoke counts derived from the applied membership changes.

Human-readable session name, topic, or generated label.

High-level session classification such as meeting, webinar, call, event, or SMS session.

Timestamp describing when the session started or is scheduled to start.

Observed external identifiers in the source system for host, organizer, or owner personas. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Observed external identifiers in the source system for participants, attendees, panelists, or registrants. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Session state such as scheduled, live, completed, canceled, or no-show.

Deep link back to the session record in the source system.

Agenda, description, or source-provided summary of what the session is about.

Timestamp describing when the session ended or is scheduled to end.

Duration of the session in whole seconds when that value is known.

Join URL or entry point for the session when one is appropriate to retain.

Reference to the team, channel, account, hub, or other organizational boundary that contains the session.

Normalized spoken transcript or transcript excerpt associated with the session.

JSON-serialized collection of linked recordings or related session artifacts.

JSON-serialized source-specific session metadata such as timezone, attendance stats, poll linkage, or telephony fields.

Name or classification of the source occurrence being captured.

Timestamp describing when the event happened.

Observed external identifiers in the source system for the personas, systems, or services that caused the event. Resolution to a persona or other actor identity is based on the source value together with each actor reference and happens in the extraction domain.

Reference to the primary thing the event happened to.

Deep link to the event in the source system when the source exposes one.

Optional short label or generated summary for the event.

Reference to the repository, project, channel, service, or other grouping context around the event.

Outcome or resulting state associated with the event when that meaning is useful.

Readable normalized event description or textual payload content.

JSON-serialized raw or normalized event payload for cases where structured details matter.

JSON-serialized source-specific event metadata such as environment, headers, batch IDs, or alert tags.

Broad business-object classification for the structured record.

JSON-serialized map of canonicalized key-value attributes that capture the record payload.

Observed external identifiers in the source system for owners, requesters, maintainers, or other linked people for the record. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Deep link to the structured record in the source system.

Best human-readable label for the record when the source exposes one.

Optional generated or source-provided synopsis of the record.

Flattened textual representation of the most important string fields for retrieval and summarization scenarios.

Current state of the record when state is meaningful.

Timestamp describing when the record was created.

Timestamp describing the most recent update to the record.

Reference to the project, service, event, repository, organization, or other grouping context for the record.

JSON-serialized source-specific attributes that should remain outside the canonical structured surface.

The absolute URI of the content item in the upstream system.

The access control entries that define who can view the content.

The source-specific entity type for this content item, such as 'markdown-file' or 'message'.

Standardized archetype envelope used for transport and storage.

The optional absolute URI-shaped container hierarchy for this content item.

Optional root-to-leaf containers with stable IDs and display names. Requires a matching hierarchy URI. If omitted, stored segments are preserved only while the hierarchy path is unchanged.

Short summary or primary human-readable description of the work item.

High-level workflow classification such as issue, incident, request, task, change, approval, or problem.

Current lifecycle state of the work item.

Timestamp describing when the work item was created.

Observed external identifier in the source system for the persona that reported, requested, or created the work item. Resolution to a persona is based on the source value together with this persona reference and happens in the extraction domain.

Observed external identifiers in the source system for current owners, assignees, or responders. Resolution to personas is based on the source value together with each persona reference and happens in the extraction domain.

Deep link to the work item in the source system.

Long-form description, body text, or normalized rich-text content explaining the work item.

Urgency or importance value supplied by the source system.

Timestamp describing the most recent source-side update to the work item.

Due date or target completion timestamp when the source tracks one.

Resolution code, closure note, or final outcome for the work item.

JSON-serialized collection of tags, components, or other categorization labels.

Reference to the project, board, service, repository, or space that owns the work item.

JSON-serialized collection of related comments, reviews, or discussion entries.

JSON-serialized source-specific workflow metadata such as severity, sprint, milestone, SLA, or custom fields.

The email address associated with the data subject for the DSR access request.

Whether matching data exists.

Additional messages.

Email addresses.

IP addresses.

Names.

Locations.

Street addresses.

Cities.

States or regions.

Countries.

Postal codes.

Company names.

Job titles.

Cookie values.

About-me content.

URLs.

Phone numbers.

Mobile phone numbers.

User IDs.

Account IDs.

Whether the account is anonymous.

Additional notes.

The email address associated with the data subject for the DSR access request.

Whether matching data exists.

Additional messages.

URI of the exported data schema.

Exported data.

The email address associated with the data subject for the DSR access request.

Whether matching data exists.

Additional messages.

Node IDs to retrieve. Duplicates are ignored.

The matching nodes keyed by node ID. Missing requested IDs are omitted.

The search query, which must contain at least one non-whitespace character.

The number of results to return.

The search algorithm to use.

The scope IDs to filter search results by.

Indicates whether the tenant search index is available for node search. This is false only when the tenant index does not exist. When this is true and results is empty, the index exists but either contains no indexed nodes or no nodes matched the query.

The search results.

Total number of matching nodes.

The ACL grant tags resolved for the requesting user. Each string is a JSON array containing the subject provider, kind, and external ID.

A persisted node.

Relative relevance score (higher is better).

Caller-owned idempotency identifier, normally the Trust onboarding-cycle ID.

Total number of source content items fetched from ContentIngestion.

Total number of source content items processed into nodes.

Total number of ContentIngestion pages fetched.

Opaque cursor to resume reprocessing from, or null when there are no more items.

Content source identifier, such as googledrive or slack. Case-insensitive.

Maximum number of matching content items to examine, including stale or failed items. Omit or set to null to process all remaining items.

Opaque NextCursor from a backfill with no failed or invalid items for the same tenant and source. Omit or set to null to start from the beginning.

Tenant IDs to remove. Duplicates are ignored.

Per-tenant deletion results.

Tenant ID.

Number of deleted node rows.

Elasticsearch indices deleted for the tenant.

Node ID.

The node text.

Signals used to classify the node.

Creation metadata for the node.

Ingestion metadata for the node.

Trust evaluation data.

Relations with other nodes.

Whether the node is deleted.

Tenant ID

Content ID.

Human-resolvable URL of this node at its external source system. Distinct from ingestionMetadata.source (the system name, e.g. "stackinternalcommunity") and ingestionMetadata.sourceId (the source's internal identifier, e.g. "5") — this is the link a human would follow to read the original content. Null when the source does not expose a stable URL.

Document-specific metadata.

Explicit user engagement data from the source system.

The external user ID.

The internal user ID.

When the content was created.

Author information.

When the content was last edited.

The document title.

The source-system score.

The source-system view count.

The content source.

The source identifier.

When the node was ingested.

Who ingested the node.

The content archetype type, when extracted from an archetype payload.

The content archetype version, when extracted from an archetype payload.

Context about the source.

The Node relation type.

The source node ID.

The target node ID.

For answer/question relations, the accepted state of the answer participating in the relation.

The source context ID.

The source context name.

The trust score from 0.00 to 1.00.

Version of the trust evaluator.

When the trust score was assigned.

A URI reference that identifies the problem type.

A short, human-readable summary of the problem type.

The HTTP status code generated by the origin server for this occurrence of the problem.

A human-readable explanation specific to this occurrence of the problem.

A URI reference that identifies the specific occurrence of the problem.

Validation errors associated with the request.

Information about a request input validation error.

The one-based page number. Values below one are treated as one.

The number of results per page, from 1 through 100.

Optional text filter, matched against name and email.

Optional exact role filter.

Optional active-state filter. Accepted values are active or deactivated.

Optional user IDs to include.

Fields the user list can be sorted by. "Name" sorts on first + last name.

Sort order: ascending or descending.

Time the validation request was created, in UTC.

Time the validation attempt was sent, in UTC.

Time the SME responded, in UTC, when recorded.

Time processing of the SME response completed, in UTC, when recorded.

Time the validation attempt expires, in UTC, when recorded.

Stable external identifier for this validation attempt. Example: validation-attempt-317.

Persisted validation request identifier.

Persisted validation attempt identifier.

Validation outcome: sme_verified when the SME approved the suggestion, or sme_updated when the SME edited it.

Tenant topic name, when one is available.

Question presented to the SME during validation.

Suggested answer captured when the validation request was created.

SME-validated answer. For sme_updated results, this is the saved edited content when available; it may be null for older edited attempts without persisted content. For sme_verified results, it matches suggestedAnswer.

External source references from the saved validation snapshot. When sourceType is supplied, only matching sources are included.

Recipient type, such as Sme or Channel.

Canonical recipient name when available; otherwise the stored recipient identifier.

Current routing attempt status.

Canonical SME name when available.

Source system or type. Example: confluence.

External document title, when available.

External source URL, when available.

Source author, when available.

Source creation or publication date, when available. Returned as a UTC timestamp.

Identifier of the message associated with the validation.

Conversation identifier associated with the validation.

Time the validation was resolved, in UTC.

The current page of SME validations with source context.

Opaque cursor for the next page, or null when there are no more results. When another match establishes more results, it continues after the last returned validation; if the scan limit is reached before an additional match is found, it continues after the last examined attempt and may accompany an empty validations array.