Glossary

TermMeaning
RequirementA structured statement with stable ID, revision, title, actor, trigger, behavior, constraints and acceptance examples
Stable IDIdentity of a requirement that never changes with its title (REQ-TEAM-001)
RevisionMonotonic integer; increases only when canonical content changes
Canonical contentThe fields that define a requirement; hashed as sorted-key JSON
SourceThe imported file a requirement came from; hashed and labelled untrusted
QuestionAn explicit unknown the stakeholders must answer
Acceptance criterionA testable example, drafted as Gherkin and unapproved until a human approves
ApprovalA local self-attested human decision about an exact revision
Evidence linkA pointer from a requirement revision to a code, test, test-run, release, ticket or PR reference
Observed fileA workspace file whose SHA-256 was recorded at link time
Imported claimA pass/fail or release outcome supplied by a person; not verified
AttestationA human statement that they reviewed the evidence for a revision
StaleApproval or evidence attached to an older revision; kept as history, no longer counts
DriftA linked file whose current hash differs from the recorded hash
Proof by proxyTreating a ticket, PR, file or status field as proof of completion
Audit chainaudit.jsonl, each event holding the previous event's hash
SealSHA-256 of an audit report's canonical content; detects later edits
VerdictPASS, PASS-WITH-FINDINGS or FAIL from the independent audit
Self-attestedIdentity typed by the user, not verified
SkillA portable SKILL.md instruction file for an AI assistant
AgentA named role definition (21 provided); not a running service
WorkflowA written execution contract (8 provided)
GateA rule enforced in code that refuses an action until conditions hold
M0..M6Milestones from the roadmap