Publish-safe: remove two disclosures, and record Nox as the answer to 006 #3

2026-08-23T19:41:04Z

jschoubben commented

2026-08-23 19:41:04 +00:00

Found by a full scan before making the repository public — the moment the public rule stops being aspirational and starts being checkable.

Two genuine disclosures removed. A module name identified a specific laptop model (hardware inventory about one installation, not a lesson that travels). And ADR 0028 named a forge username in a repository path, which the public rule forbids — the sentence had also gone stale, since that repository was subsequently verified empty of anything unique and removed. Removing a disclosure from a record is the same class as fixing a path; the rule permitting it outranks the one forbidding edits.

Issue 006 gains its proposed direction: Nox works from within this repository rather than these documents being synced into the knowledge base. Better on three counts — no copy so no drift, no fourth knowledge system (which was the original objection), always current.

But it changes the promise, and the issue says so rather than glossing it. ADR 0019 promised these documents would surface beside everything else in a symptom search. An agent that must be asked is reachable, not surfacing — and the two differ in exactly the case the operational memory exists for: someone debugging an error with no reason to suspect HQ knows anything about it.

Found by a full scan before making the repository public — the moment the public rule stops being aspirational and starts being checkable. **Two genuine disclosures removed.** A module name identified a specific laptop model (hardware inventory about one installation, not a lesson that travels). And ADR 0028 named a forge username in a repository path, which the public rule forbids — the sentence had also gone stale, since that repository was subsequently verified empty of anything unique and removed. Removing a disclosure from a record is the same class as fixing a path; the rule permitting it outranks the one forbidding edits. **Issue 006 gains its proposed direction:** Nox works from within this repository rather than these documents being synced into the knowledge base. Better on three counts — no copy so no drift, no fourth knowledge system (which was the original objection), always current. But it changes the promise, and the issue says so rather than glossing it. ADR 0019 promised these documents would surface *beside everything else* in a symptom search. An agent that must be **asked** is reachable, not surfacing — and the two differ in exactly the case the operational memory exists for: someone debugging an error with no reason to suspect HQ knows anything about it.

jschoubben referenced this issue from a commit

2026-08-23 19:41:12 +00:00

Merge pull request 'Publish-safe: remove two disclosures, and record Nox as the answer to 006' (#3) from chore/publish-safe into main

jschoubben closed this pull request

2026-08-23 19:41:12 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#3