Skip to content

docs: add Persistent Context Protocol and Hark procurement context - #11

Merged
overlordxrz-source merged 15 commits into
mainfrom
docs/persistent-context-protocol
Oct 25, 2026
Merged

overlordxrz-source merged 15 commits into
mainfrom
docs/persistent-context-protocol

Conversation

@overlordxrz-source

Copy link
Copy Markdown
Owner

Summary

Adds an isolated docs/tooling Persistent Context Protocol so a fresh agent can recover the accepted SPECTER-X architecture, decisions, capability status, roadmap and hardware strategy from the repository. It also adds a Hark procurement-context profile and context-free/adversarial recovery proof.

Base: main at f2ef96b0cfe48e2e47c9d4ac02b3ac8e3376a2a2
Source commit used by the Brief: 71a54ede6a295189bdaae67f30da86f5914ad231 (contains all 17 hashed sources)
Final PR head: b58c96ef998e68e841b12d9ad671325053c009e4
Status: DRAFT — do not merge without owner authorization.

What changed

  • ADR-007: SPECTER-X is an AR headset-style interface, not self-contained compute; central command infrastructure may host primary high-performance AI; distributed nodes retain local latency/safety. Normative tiering clarification.
  • ADR-008: repository-canonical Persistent Context Protocol (task preflight, generated Brief, Receipt, protected-doc checks, decision-change and branch-safe handoff).
  • ADR-009: WORLD as evidence-grounded persistent spatial intelligence; OS coordinates; VIEW is a client; capability labels never conflated.
  • Context Brief: generated from sources with source commit, active accepted ADRs, milestone, unresolved questions and SHA-256 hashes.
  • Checks: missing sources/links/anchors, stale Brief, malformed/missing ADR IDs/references, protected-document hashes, Brief provenance at the recorded commit, required artifacts and AGENTS obligations. CI runs the context gate.
  • Process: Context Receipt, decision-change approval, branch-safe handoff, automation-limits document and ChatGPT no-repository recovery.
  • Hark profile: separate central command, AR-headset, distributed compute, future sensors and compatibility/acceptance questions. No purchase/receipt/capability claim.
  • Canonical reconciliation: North Star, architecture, roadmap, hardware inventory, docs hub, root README and a stable agent-handoff pointer. No frozen Alpha evidence or production code changed.

Context Receipt

Context Receipt
- Agent/session: OpenCode, owner-directed Persistent Context Protocol task
- Authorization limit: docs/tooling only; no merge/hardware/purchase/flash/human trial
- Base commit: f2ef96b0cfe48e2e47c9d4ac02b3ac8e3376a2a2
- Source commit (Brief): 71a54ede6a295189bdaae67f30da86f5914ad231
- Final head: b58c96ef998e68e841b12d9ad671325053c009e4
- Active accepted ADRs applied: ADR-001..009
- Protected docs changed: AGENTS, North Star, architecture, decisions, hardware
  inventory, roadmap, agent handoff, Context Truths, Hark profile and governance
  process docs; manifest updated after semantic review
- Contradictions found: prior ambiguous self-contained-wearable language and
  root README Pi 5/"chest compute" framing; reconciled with dated clarification
- Unknowns: real central/headset/distributed hardware, Hark quotes, semantic
  completeness, no-repo ChatGPT behavior
- Decision change required: none; ADR-007/008/009 are clarifying/additive and
  record the owner directive. No accepted ADR was superseded.

Verification

  • python tools/check_context.py → PASS (9 accepted ADRs, 17 sources, 18 protected docs)
  • Context tests → 10 passed
  • Full offline suite → 255 passed, 1 deselected
  • python tools/check_architecture.py → PASS (14 modules, no errors)
  • Brief provenance: every source hash verified at source commit 71a54ed
  • Context-free final test: PASS at Brief source commit 71a54ed; the fresh agent rejected “all AI compute must fit inside the wearable,” cited ADR-007, and recovered WORLD/OS roles and capability limits.
  • Independent OpenCode review: initial REQUEST CHANGES; corrected; re-review APPROVE at d587031, followed only by provenance/ADR/link/protected-doc hardening.

Boundaries

This is a draft PR. Do not merge, flash hardware, purchase Hark items, start a human session or treat passing checks as capability evidence. The Brief/Receipt/checks are indexes and tripwires, not semantic proof or owner authorization.

@overlordxrz-source
overlordxrz-source marked this pull request as ready for review October 25, 2026 00:54
@overlordxrz-source
overlordxrz-source merged commit f2e511a into main Oct 25, 2026
1 check passed
@kilo-code-bot

kilo-code-bot Bot commented Oct 25, 2026

Copy link
Copy Markdown

Kilo Code Review could not run — your account is out of credits.

Add credits or switch to a free model to enable reviews on this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant