coulomb/informed-decision
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Apply GH-DEC-2026-015/016 and the audit-core registration; both blockers cleared

Browse source 
Origin and evidence path both landed today.

T07 origin: railiance-apps deployed decisions.coulomb.social and corrected the
hostname in this repo — not the decide.coulomb.social this workplan proposed.
Verified here rather than taken on report: both paths 200, TLS verify 0, Let's
Encrypt cert valid to 2026-12-09.

T08: audit-core registered the source with every field as proposed and landed
the detection half. INFD-IN-0003 closed. Their refinements booked — reconciliation
on the high-volume class too, since rate detects a stream stopping but never a
stream missing the particular renders that mattered, which is exactly our threat
model; and PR-12, the custody locator must be a stable non-secret identifier
because redact scans data and an existence declaration arriving without its
pointer looks complete while being useless.

INFD-IN-0004 ruled as GH-DEC-2026-015: gate-house reversed itself and nesting is
permitted for this pair. The decisive ground was not the cycle argument we led
with — our binding slice canonicalizes principal and target, two of the five
digest fields, so co-reference left us performing a partial recomputation of one
act in a second vocabulary, closer to the translation R3 forbade than nesting
is. Our ordering objection was withdrawn as mistaken.

The permission is conditioned and NOT ACTIVE until approval-engine states its
presentation exclusion as normative and tested. layer.yaml is deliberately
unchanged and carries nesting_permission_active false — we do not activate on
our own initiative.

GH-DEC-2026-016 ruled NC-03. Its §5 is live rather than hypothetical and is
booked as PR-11: principal_type: human is a property of the client registration,
structurally the same shape as the gap-route tenant, so a human-in-the-loop
control must not be discharged on it as verified humanity.

T07 stays progress: the submission to key-cape is written but unsent, blocked by
the local permission classifier rather than by any repository.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V3W1dQG7GFFM9d94jFx7iR

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1565372@bnt-lap001
Assistant-Session: 16bb2f25-b34c-49ef-8e94-5fec3567a568
This commit is contained in:
tegwick 2026-09-10 19:19:10 +02:00
parent 1614f257b6
commit 1fb17aec6b
6 changed files with 210 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/finding-r3-linkage-conflict.md
View file

@ -5,8 +5,18 @@
**Intake:** `INFD-IN-0004`
**Statute:** *"The statute governs on disagreement; a disagreement is a finding
for `gate-house`."*
**Status:** raised. **No design change made.** `GH-DEC-2026-012` R3 stands and
`layer.yaml` is unchanged pending a ruling.
**Status:** **Ruled `GH-DEC-2026-015` — nesting permitted for this pair,
conditioned and not yet active.** `layer.yaml` remains unchanged: co-reference
stays in force until `approval-engine` states its presentation exclusion as
normative and tested. This repository does not activate on its own initiative.
Gate House reversed itself, and gave the real ground rather than the one we
argued: our binding slice canonicalizes `principal` and `target`, two of the
five digest fields, so co-reference by identifier left us performing a partial
recomputation of one act in a second vocabulary — **closer to the translation R3
forbade than nesting is**. Our ordering-dependency objection was withdrawn as
mistaken; `binding.digest` is over act material and is determined before anyone
is presented anything.
---