Repository navigation
docs: add Persistent Context Protocol and Hark procurement context - #11
Merged
Merged
Conversation
Fix PR11 context freshness coverage and ADR status acceptance
overlordxrz-source
marked this pull request as ready for review
October 25, 2026 00:54
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
mainatf2ef96b0cfe48e2e47c9d4ac02b3ac8e3376a2a2Source commit used by the Brief:
71a54ede6a295189bdaae67f30da86f5914ad231(contains all 17 hashed sources)Final PR head:
b58c96ef998e68e841b12d9ad671325053c009e4Status: DRAFT — do not merge without owner authorization.
What changed
Context Receipt
Verification
python tools/check_context.py→ PASS (9 accepted ADRs, 17 sources, 18 protected docs)python tools/check_architecture.py→ PASS (14 modules, no errors)71a54ed71a54ed; the fresh agent rejected “all AI compute must fit inside the wearable,” cited ADR-007, and recovered WORLD/OS roles and capability limits.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.