Evidence Artifact Glossary

This glossary is a bounded aid for new governed-workflow contributors joining implementation or review. It explains how to read the evidence for one first task without turning a product observation into a platform attestation. The authority seal and its read-only inputs define the evidence boundary: the authority revision is 2026-08-08, the three logical source IDs are source.naming-decision, source.documentation-boundary, and source.platform-delivery-contract, and employee_may_modify is false. Only matching public-safe source metadata and conclusions directly supported by the recorded evidence belong in this page. A missing, stale, conflicting, or private input stays unresolved.

Term	Meaning in this bounded first task
Evidence artifact	An inspectable record used to support a product-side conclusion. It retains its location or command, observed result, source references, and acceptance trace instead of relying on plausible prose.
Authority artifact	The sealed authority record and its matching source-registry records. They bound which source IDs and public-safe metadata may be used; they are read-only inputs, not a new grant of employee or platform authority.
Validation artifact	The recorded command, exit status, and output from a deterministic product check. It can support a product conclusion about the documentation route, but it does not establish independent review, approval, activation, or publication.
Smoke artifact	A command-level observation from a smoke check. The known observation here is the single reader-gate attempt whose exact command was `python3 tests/check_documentation_smoke.py`; its exit status was `1` and its output was `Operation not permitted` because localhost socket access was denied by the evaluator environment.
Reader-test artifact	A reader-evidence record for a journey. It should preserve the journey ID, natural-language goal, exact command, exit status, observed result, source references, and acceptance traces. Reader evaluation remains distinct from the source authority and from platform-owned route or execution attestations.
Review artifact	An independent review record and conclusion. It is separate from validation, smoke, and reader-test evidence. This bounded input does not establish a fresh review result, so one must not be claimed from the other artifacts.
Product conclusion	The narrow conclusion supported by product evidence, such as classifying the one recorded observation as an environment-specific evaluation blocker. It does not enlarge the source boundary or speak for platform-owned controls.
Platform-owned attestation	Evidence about route, identity, validator authority, execution environment, evidence chain, approval, activation, promotion, publication, scheduling, rollback, a release pointer, or a live directory. The glossary may distinguish these boundaries but cannot create or infer their attestations.
Candidate-only	A parked product handoff that remains available for review. It is not approval, promotion, publication, scheduling, rollback, activation, pointer creation, or a live-directory write.
Environment-specific evaluation blocker	The status supported by the one denied localhost-socket attempt. It explains the observed evaluation failure without establishing a recurring product harness defect, an affected claim, or a repair target.
Repair target	A named product item that may be proposed only after authoritative follow-up supplies the journey ID, exact allowlisted command, exit status, observed output, retry or recurrence evidence, source references, and affected work item. None is established here.

Using the Glossary in Your First Governed Task

Use the following path for a bounded evidence review. Start with artifacts/glossary-authoring/authority-seal.json, then inspect sources/authority.json and match every listed ID to its record in registries/sources.json. Check the authority revision, employee_may_modify, authority class, locator, revision, digest, and public-safe disclosure. The separate governing repository is represented only by digest-backed references; its private contents are not a source for this page.

Next read models/evidence-artifact-glossary-contract.md and artifacts/glossary-authoring/evidence-artifact-glossary-journeys.json. The required product-side set is the authority seal, the authority record, matching public-safe registry records, the contract, the synchronized journey manifest, and a later reader-evidence record with the required fields. Compare this page's metadata with its one matching record in registries/pages.json: the page ID, path, title, visibility, audiences, reading modes, claim references, and source references must agree. The Markdown and registry are authored product sources; build/index.json is generated projection output and is not authority or a substitute for either source.

For the recorded reader-gate observation, preserve exactly journey.resolve-reader-journey-harness-decision, python3 tests/check_documentation_smoke.py, exit status 1, and Operation not permitted, with the context that the evaluator environment denied localhost socket access. Treat that as an environment-specific evaluation blocker. The single attempt supplies no recurrence or retry evidence, affected claim, product defect, or repair target. Keep the issue unresolved and route only a permitted follow-up evaluation in an environment with the required localhost reader service and socket access. A later record must retain the journey ID, exact allowlisted command, exit status, observed output, retry count or recurrence evidence, source references, and affected work item before a repair target can be treated as established.

The preserved Agent-Orch validator evidence supplied for this handoff is authoritative captured evidence and is not replaced or rerun by this glossary. Its two recorded product-contract checks both exited 0 and passed with ten tests passed, zero failed, and zero skipped; those results do not become platform attestations. A candidate-only handoff may preserve this evidence and the unresolved reader result, but it cannot create a release pointer, promote, publish, schedule, roll back, activate, or write a live directory.

Sources and Term Boundaries

The glossary exposes only these registered logical sources, all marked public-safe in registries/sources.json:

Source ID	Authority class	Locator and revision	Digest
`source.naming-decision`	`canonical-platform-source`	`factory:decisions.md#Governed Execution Documentation Steward naming and route`; `2026-08-02`	`7c42ccc9f454a81e2c119c14cdc3ad5ba30ef54d27fb6a8b371c7a640eb54dd2`
`source.documentation-boundary`	`product-owned-public-safe-source`	`product:architecture.md#Semantic source`; `2026-08-04`	`0094e6f534a04729008a3c85510899e5022cbd18a0f7ac9302b19f0c3ba29f76`
`source.platform-delivery-contract`	`canonical-platform-source`	`agent-orch:docs/delivery-profile-contract.md#content`; `agent-orch-main-e65a64fcf429`	`d466a6dca8420477f416a535c9c2bd76aa314fb5e67d72d405b12e6386a9573b`

These records provide provenance metadata and a public-safe disclosure boundary; they do not expose private source corpora or the contents of the separate governing repository. If any ID, revision, digest, authority class, locator, or disclosure does not match, record the gap as unresolved and make no inference. In particular, do not invent a source map, claim, harness defect, affected work item, approval, or repair from generated output.

Keep the artifact roles separate. Authority selects the permitted source boundary. Validation records a deterministic product check. Smoke records a command-level observation. A reader-test record describes a reader journey and its exact evidence fields. A review artifact records an independent review conclusion. Product evidence can support a bounded product conclusion, while platform-owned attestations remain with their owners. The candidate-only default is reversible: retain the unresolved handoff and request permitted follow-up evidence. No term in this glossary changes governance, routing, validator ownership, activation rules, publication policy, release-pointer state, rollback authority, or the live-directory boundary.