Skip to content

feat(policy): stage the fail-closed visibility kernel (un-imported) - #46

Open
DarrenZal wants to merge 1 commit into
regen-prodfrom
recover/visibility-policy-kernel
Open

feat(policy): stage the fail-closed visibility kernel (un-imported)#46
DarrenZal wants to merge 1 commit into
regen-prodfrom
recover/visibility-policy-kernel

Conversation

@DarrenZal

Copy link
Copy Markdown
Contributor

Recovered from the NUC runtime snapshot (nuc-runtime@316f2e2).

These files existed only inside the NUC's .git. No MacBook clone had them (koi-processor-service, RegenAI/koi-processor, koi-processor-runtime all checked), and the newest tarball backup predated them by 2.5 months. Provenance: they were MacBook working-tree scratch, rsynced to the NUC by dobby/scripts/deploy.sh, then lost locally — see ~/.claude/plans/koi-infra-entity-type-hints-handoff.md:36, which lists several as "untracked scratch in the working tree (operator to triage — NOT committed)".

Purely additive: no existing file is modified, nothing is imported or wired up, no migration is applied. Merging changes no runtime behaviour.

A coherent, staged, deliberately-undeployed feature (Phase 1 KG two-viewport): a 316-line fail-closed visible_at(...) kernel with 277 lines of tests, its backfill script, and the read-path swap map documenting the 10 call sites it targets.

Runtime-dead, not repo-dead. Nothing in api/ or scripts/ imports it; tests/test_visibility.py and scripts/backfill_visibility_107.py do. Its own handoff says "Un-imported (nothing uses it yet)." The five files move as one unit — dropping api/policy/ alone breaks test collection.

Ship with or after the migrations PR. Do not apply the 10 read-path swaps as part of merging this.

Recovered from the NUC runtime snapshot (nuc-runtime@316f2e2). These files existed ONLY in the NUC's .git — no MacBook clone had them, and the newest tarball backup predated them by 2.5 months. Additive: no existing file is modified.
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