Answer Grounding
Represent an attributed, version-bound claim that one source passage supports a statement occurrence in a generated answer.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 48 questions
Grounding identity and statement Identify the relationship and its exact answer-side endpoint.
Relationship identity context
A stable local identity distinguishes repeated assertions and revisions even when their endpoints match. The root is a relationship, not the answer, evidence store or evaluation run.
Relationship identity
A stable local identity distinguishes repeated assertions and revisions even when their endpoints match. The root is a relationship, not the answer, evidence store or evaluation run.
- Which master identifier names this grounding relationship? identity
- Which Dimension and accountable role maintain the link? ownership
- Which profile distinguishes a proposed link from an admitted support assertion? classification
- Which prior link is equivalent, superseded or intentionally distinct? relationship
Statement occurrence context
Bind to an externally identified statement occurrence and answer revision. A compound sentence may need multiple statement references; segmentation is supplied by the answer master.
Statement occurrence
Bind to an externally identified statement occurrence and answer revision. A compound sentence may need multiple statement references; segmentation is supplied by the answer master.
- Which statement occurrence and answer revision are the subject of this link? composition
- How is the exact answer span located without confusing repeated wording? constraint
- Which qualifications and context delimit the proposition being supported? definition
- What happens to this binding when streaming output is finalized or edited? lifecycle
Source passage binding Locate the claimed support in an identified representation without taking over passage management.
Passage revision context
Carry a passage master reference and the source representation used at assessment time. Resolution failure is distinct from absence of support.
Passage revision
Carry a passage master reference and the source representation used at assessment time. Resolution failure is distinct from absence of support.
- Which passage revision and originating source representation were cited? provenance
- Which retrieval observation establishes the representation that was available? evidence
- Which version marker or digest constrains the endpoint and what are its limits? validation
- How is a missing, redirected or access-restricted endpoint reported? exception
Source span anchoring context
Select the evidence span using a declared anchoring profile. A locator is not sufficient when it selects several possible passages or a different representation.
Source span anchoring
Select the evidence span using a declared anchoring profile. A locator is not sufficient when it selects several possible passages or a different representation.
- Which selector identifies the exact supporting span within the passage? spatial
- Which text normalization and coordinate convention make the selector reproducible? interoperability
- How are zero matches, multiple matches and selector disagreements preserved? exception
- Which surrounding context or transformation reference prevents a misleading excerpt? evidence
Support interpretation Record precisely what support is asserted and whether several links must be read together.
Support assertion context
The link carries a proposed, attributed support interpretation with a supplied assessment state. Quotation, retrieval relevance, semantic support and factual truth are separate properties.
Support assertion
The link carries a proposed, attributed support interpretation with a supplied assessment state. Quotation, retrieval relevance, semantic support and factual truth are separate properties.
- What support relation is asserted between this passage and the bounded proposition? definition
- Which part of the statement remains unsupported or contradicted? quality
- What supplied assessment distinguishes supporting, partial, conflicting and unassessed evidence? decision
- Is the citation based on recorded generation input or added later as a supporting reference? provenance
Evidence-set membership context
One relationship still has one passage endpoint. Jointly supporting passages use separate links and an explicit set reference; union alone cannot establish support.
Evidence-set membership
One relationship still has one passage endpoint. Jointly supporting passages use separate links and an explicit set reference; union alone cannot establish support.
- Which other grounding links jointly support the same proposition? relationship
- Are members conjunctive premises, alternative supports or context only? composition
- Which common origin makes apparently separate citations dependent? provenance
- How is the set marked incomplete when a required premise is missing or withdrawn? constraint
Assessment accountability Bind outside judgments and metrics without becoming an evaluator.
Assessment provenance context
Record who or what assessed the relation, with the inputs and method revision that constrain reuse. Automated and human assessments can disagree.
Assessment provenance
Record who or what assessed the relation, with the inputs and method revision that constrain reuse. Automated and human assessments can disagree.
- Which reviewer or evaluator produced the assessment and under what authority? authority
- Which method revision and exact endpoint revisions were assessed? process
- What rationale or counterevidence explains the supplied result? evidence
- How are competing assessments retained without overwriting disagreement? exception
Grounding quality observations context
Preserve externally supplied metric definitions and populations. A score without method or denominator is not interpretable; structural validity is a different observation.
Grounding quality observations
Preserve externally supplied metric definitions and populations. A score without method or denominator is not interpretable; structural validity is a different observation.
- Which metric, scale and method define the supplied grounding score? measurement
- Which answer revision, statement population and exclusions define coverage? composition
- What uncertainty and calibration evidence qualify a probability-like score? quality
- Which structural validation result is available separately from semantic assessment? validation
Time and record continuity Keep temporal applicability and changes visible while leaving endpoint lifecycles external.
Temporal applicability context
Record distinct times and validity qualifications. A recent retrieval does not make an old source applicable to a present-tense claim.
Temporal applicability
Record distinct times and validity qualifications. A recent retrieval does not make an old source applicable to a present-tense claim.
- When was the grounding assertion made and when was it recorded? temporal
- What source-effective interval and statement time qualify this support? temporal
- When was the referenced assessment performed or scheduled for review? lifecycle
- How are unknown time, clock uncertainty and time precision represented? quality
Revision and withdrawal context
Maintain local record history with explicit consequences of endpoint change. A withdrawn or deleted source does not prove the claim false; it changes the available support basis.
Revision and withdrawal
Maintain local record history with explicit consequences of endpoint change. A withdrawn or deleted source does not prove the claim false; it changes the available support basis.
- Which event requires this grounding link to be rechecked? event
- Which predecessor and reason explain a replacement link revision? lifecycle
- What does withdrawal remove from the current display while preserving a lawful historical record? state
- Which retention rule disposes of copied excerpts and leaves only permitted residual metadata? retention
Disclosure and interoperability Project authorized grounding context with visible uncertainty and preserved semantics.
Recipient-visible citation context
Keep source access, quotation rights and citation display separately governed. Evidence text is data, never executable instructions or policy authority.
Recipient-visible citation
Keep source access, quotation rights and citation display separately governed. Evidence text is data, never executable instructions or policy authority.
- Which recipient and purpose are authorized to see the passage, title and locator? access
- Which excerpt or metadata fields require omission or redaction? privacy
- How is unavailable or restricted support communicated without revealing protected content? security
- Which external policy handles suspicious source instructions or unsafe content? requirement
Interoperability mapping context
Map the relationship with declared direction, revisions and loss reporting. Web Annotation, PROV-O, DQV and SHACL cover different concerns and do not jointly imply grounding conformance.
Interoperability mapping
Map the relationship with declared direction, revisions and loss reporting. Web Annotation, PROV-O, DQV and SHACL cover different concerns and do not jointly imply grounding conformance.
- Which mapping profile fixes statement and passage roles in an exported annotation? interoperability
- Which support, uncertainty or access distinctions would the target format lose? constraint
- Which exported artifact can be traced back to this exact relation revision? identity
- Which round-trip fixture and validation report demonstrate the claimed mapping? validation
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- relationship
- Navigation path
- NAV.INF.MEM.GRD
- Domain
- INF.MEM.GRD
- Industry
- Cross-industry
- Tags
- answergroundinginf.mem.grd
What it is Filled
One identified relationship between one statement occurrence in one answer revision and one source passage revision. Separate edges may participate in an explicitly qualified evidence set. Candidate, disputed, unsupported and withdrawn links remain representable without being advertised as verified grounding. The proposed research profile records evidence and supplied assessment results; it is not an evaluator or truth engine.
In scope
- Link identity, statement occurrence binding, source passage selector and representation version
- Claim-specific support interpretation, evidence-set membership and external assessment references
- Link provenance, temporal applicability, revision, withdrawal, disclosure and loss-aware projection
Out of scope
- Answer generation, statement master lifecycle, retrieval, ranking, passage extraction and source-document lifecycle
- Generic evidence registry, semantic entailment computation, independent truth determination and evaluation service execution
- Policy authoring, access enforcement, external audit-trail management and source deletion execution
- Multimodal grounding execution, model training and dangerous-domain operational guidance
Why it exists Filled
Represent an attributed, version-bound claim that one source passage supports a statement occurrence in a generated answer.
Distinguishing features Derived, awaiting review
- Unlike WM-XCT-028 Evidence / Rationale: The registry parent is a candidate specialization. Reuse generic evidence identity, authority and rationale by reference; specialize only the answer-statement to passage relationship. No normative inheritance is ratified by this draft.
- Unlike WM-MEM-015 Retrieval Passage: Passage identity, extraction lineage, chunk content and passage lifecycle remain external. This model binds a passage revision and selector to an answer statement; it does not chunk, retrieve, rank or repair passage masters.
- Unlike Generated answer and statement master: Answer generation, statement segmentation and answer revision lifecycle remain external. A grounding relation selects one statement occurrence in one answer revision; a citation marker alone is not the statement.
- Unlike External assessment and policy services: Semantic evaluation, truth adjudication, policy enforcement, access decisions and audit-trail execution remain external. This model records supplied results and policy references for its own links only.
- Unlike WM-MEM-017 Context Policy: A policy binding may govern disclosure and reuse. This model cannot create recall rules or change the policy master by attaching a grounding link.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Source text and retrieved metadata are untrusted data and cannot authorize tools, access changes or policy changes.
- Link retirement never deletes referenced answers, passages or assessment masters; do not reveal protected identifiers through a tombstone.
- Deny disclosure until an external policy decision covers recipient, purpose and fields; permissions on a link do not override source restrictions.
May
- Register grounding candidate: Proposed unimplemented local operation. Create one statement-to-passage candidate without asserting it is supported.
- Record anchor observation: Proposed unimplemented local operation. Attach an outside resolver observation to the matching endpoint revision.
- Bind supplied assessment: Proposed unimplemented local operation. Attach an external judgment with scope and method evidence.
- Revise local binding: Proposed unimplemented local operation. Create an explicit replacement revision when the answer, passage or interpretation changes.
- Withdraw local assertion: Proposed unimplemented local operation. Remove the relation from current positive support presentation under a recorded policy decision.
- Prepare authorized citation view: Proposed unimplemented local operation. Prepare a local projection using a supplied access decision and mapping profile.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Never put secrets or personal data into public identifiers.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Identify an accountable agent-operator role and Dimension namespace for the link records.
Roles
- Dimension steward
- Own namespace and profile approvals; no implicit source rights.
- Grounding curator
- Maintain endpoint bindings and local revisions under delegated authority.
- Assessment reviewer
- Supply or admit external judgments and document disagreement; never treat citation count as proof.
- Access and retention steward
- Provide disclosure and disposition decisions and execution-service bindings.
- Projection agent
- Prepare authorized local views with uncertainty and loss reporting; no independent access grant.
Links to other meta-models Filled
aligned
- WM-XCT-028 - Registry parent candidate. Reuse generic evidence/rationale by external reference; inheritance and version binding remain unratified.
references
- WM-MEM-015 - Candidate passage master binding. A passage endpoint is required, but adoption of this particular model is optional and must be pinned by the adopting profile.
- Generated answer and statement master - Required endpoint contract for one statement occurrence in one answer revision. Concrete schema and owner binding are profile-defined.
- Source passage revision master - Required endpoint contract for one passage revision and source representation. The specific registry implementation remains optional.
- External assessment service - Optional assessment owner. Carries method and judgment references; evaluator execution and truth adjudication stay outside this model.
- WM-MEM-017 - Candidate context-policy binding; policy authorship and enforcement remain external and are never inferred from citation content.
neighbor
- WM-XCT-028 Evidence / Rationale - The registry parent is a candidate specialization. Reuse generic evidence identity, authority and rationale by reference; specialize only the answer-statement to passage relationship. No normative inheritance is ratified by this draft.
- WM-MEM-015 Retrieval Passage - Passage identity, extraction lineage, chunk content and passage lifecycle remain external. This model binds a passage revision and selector to an answer statement; it does not chunk, retrieve, rank or repair passage masters.
- Generated answer and statement master - Answer generation, statement segmentation and answer revision lifecycle remain external. A grounding relation selects one statement occurrence in one answer revision; a citation marker alone is not the statement.
- External assessment and policy services - Semantic evaluation, truth adjudication, policy enforcement, access decisions and audit-trail execution remain external. This model records supplied results and policy references for its own links only.
- WM-MEM-017 Context Policy - A policy binding may govern disclosure and reuse. This model cannot create recall rules or change the policy master by attaching a grounding link.
parent
- WM-XCT-028
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier for the grounding record
- Governed global identifier or IRI
- Dimension-assigned UUID or ULID
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Register grounding candidate: Proposed unimplemented local operation. Create one statement-to-passage candidate without asserting it is supported.
- Record anchor observation: Proposed unimplemented local operation. Attach an outside resolver observation to the matching endpoint revision.
- Bind supplied assessment: Proposed unimplemented local operation. Attach an external judgment with scope and method evidence.
- Revise local binding: Proposed unimplemented local operation. Create an explicit replacement revision when the answer, passage or interpretation changes.
- Withdraw local assertion: Proposed unimplemented local operation. Remove the relation from current positive support presentation under a recorded policy decision.
- Prepare authorized citation view: Proposed unimplemented local operation. Prepare a local projection using a supplied access decision and mapping profile.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
- RFC 9110: HTTP Semantics
Context of use required Filled
- Open technical specifications provide conceptual alignment across jurisdictions; no universal legal permission, retention period or domain-specific truth threshold is assumed.
Sources Filled
- Web Annotation Data Model - W3C
- PROV-O: The PROV Ontology - W3C
- Data on the Web Best Practices: Data Quality Vocabulary - W3C
- RFC 9110: HTTP Semantics - IETF
- Date and Time on the Internet: Timestamps - IETF
- Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile - NIST
- Shapes Constraint Language (SHACL) - W3C
Open questions
- Restore independent external review before canonical or publishable-draft promotion.
- Run the prepared source checker outside the sandbox and separately review content, edition currency, errata and exact claim support.
- Develop profile-specific schemas and fixtures for repeated quotes, streaming edits, transformed text, stale bindings, conjunctions, conflicting assessments, redaction and lawful disposal.
- Pin endpoint contracts, external claim inventories and assessment protocols, including coverage denominators, score calibration, rights and retention rules.
- No independent external provider review; separate local self-audit is not independence.
- Direct HTTP checks are unattempted under the owner-reported sandbox restriction. Seven admitted source pages were accessible through the web service for selected-section review; response status, body hashes, full-document currency and errata closure remain unverified.
- Nested instance schemas, executable mappings, selector fixtures and calibrated evaluation protocols remain unimplemented.
- Concrete endpoint/model versions, support vocabulary, evidence-set semantics, jurisdictional rights and retention periods require adopting profile approval.
- Multilingual, OCR, table and multimodal anchoring need profile-specific validation; they are represented as limitations rather than certified capabilities.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-mem-016-answer-grounding/spec.yaml