docs: add authority and trust glossary

[xiaoyu607]

Summary

Add the fourteen terms requested in #17 to docs/GLOSSARY.md, with links to the public source contracts, and add an entry under README Architecture.

The glossary preserves reachability ≠ identity ≠ admission ≠ authority ≠ execution and distinguishes proposals, capability advertisements, peer admission, evidence, and GETIG frames from execution authority. It describes implementation boundaries without making security or production-readiness guarantees.

The closing guidance labels the Phase-0 boundaries document as historical and directs readers to README for current capabilities and limitations, so its old no-federation/no-mesh scope is not read as a current limit.

Addresses #17. Prepared against 2a977fe34c427ce3f544963b505d887fc890df1e.

Scope

• Documentation / examples only
• Tests / tooling
• CLI / developer experience
• Runtime behavior
• Policy / authority / security boundary
• Dependency / CI / supply chain
• Governance

Only docs/GLOSSARY.md and README.md change.

Verification

AI agent checks: source definitions and all relative links; fourteen requested terms; README entry; git diff --check; isolated patch application check.

• pnpm typecheck
• pnpm build
• pnpm test — 108 files passed, 2 skipped; 3,006 tests passed, 25 skipped
• Relevant targeted tests — documentation only
• CI / Security reviewed for this contribution

Local environment: macOS, Node 22.23.2, pnpm 10.11.1. Dependencies installed from the official npm registry with frozen lockfile and lifecycle scripts disabled. Initial sandbox run failed because of temporary-directory symlink/path handling and blocked local listeners. Retried with a canonical temporary root and local listener permission; the suite passed. No assertions or runtime source were changed. Test-generated evidence fixtures were restored and are excluded from the commit. Platform-specific skipped tests were not treated as passes.

Authority and security impact

Documentation only. No runtime behavior, policy, capability, isolation, cryptography, network trust, secret handling, or evidence contract changes. An approval requirement is distinguished from completed human approval.

AI assistance

• No material AI assistance
• AI materially assisted this contribution

Tool/model: OpenAI Codex, GPT-6 family; exact backend variant was not exposed to this session. The glossary, README addition, source analysis, verification, and PR description were materially AI-assisted.

Human verification: the contributor reviewed all fourteen definitions against their sources and reported no misunderstandings or exaggerated security guarantees. They confirmed that approval requirements, communication trust, routing and visual projection are not conflated with execution authority. Their review requested the historical Phase-0/current README distinction in the closing guidance; this revision implements that request. AI checks and automated tests are separate from this reported human review. This PR remains a draft; no reviewer request is being made.

Provenance

Prepared using public repository source only; no private customer/chat data, secrets, or additional third-party material was included. Existing documentation licensing metadata applies; no licensing files were changed. Human contributor confirmation of licensing/provenance responsibility remains pending.

Known limitations

Experimental implementation, not a security proof or production readiness claim. GETIG's current entity projection leaves event/proposal-flow collections empty. The fourteen definitions have contributor-reported human source review. The closing guidance now distinguishes historical Phase-0 boundaries from current README limits. This PR's CI/Security review remains pending.

[Matrix-Engage]

Thank you, @xiaoyu607, for your contribution to Menog OS.

I have reviewed the changes in docs/GLOSSARY.md and README.md against the acceptance criteria of Issue #17.

Review findings:

• All 14 requested terminology definitions are covered.
• The separation of reachability, identity, admission, authority, and execution is preserved.
• Documentation references are aligned with the public architecture.
• Historical Phase-0 boundaries are distinguished from current implementation capabilities.
• No runtime code, security policy, execution authority, dependencies, or CI configuration has been modified.
• All six required CI and Security checks have passed on commit 19bf933e.
• The PR is mergeable with no reported conflicts or unresolved review threads.

The contributor's licensing and provenance responsibility has been confirmed in accordance with the repository's contribution requirements.

Decision: APPROVED FOR MERGE INTO main.

This approval is limited to the documentation changes in this PR and does not constitute production-readiness or security certification.

Thank you for helping make Menog OS more accessible, transparent, and understandable to new contributors.

— Menog OS Maintainer