047-shared-secret-detector-convergence
Converge secret detection upward: aicortex's detectors move into action-gate, and aicortex consumes them
aicortex-gate carries its own credential detectors (013 B-4, `rules.rs`, `secrets.rs`), and action-gate-core, the family's pure action gate, ships a weaker `SecretsCheck` with an overlapping pattern set. The owner chose to converge upward: aicortex's stronger detectors, with their detector ids, byte offsets, and full private-key marker set, move into action-gate under a separate upstream spec, and aicortex-gate then consumes action-gate's table at an exact pin instead of keeping its own. The consumption is admissible only at parity with 013's committed corpus, and aicortex keeps its own verdict, normalization, and keyed-digest ledger record. Until the upstream release exists this spec is blocked, not mocked.
Read the full pinned specification ↗Relationships
depends on
Claimed units
- establishes
{ "kind": "file", "path": "crates/aicortex-gate/tests/registry.rs" } - extends
{ "nature": "additive", "spec": "013-write-gate-and-redaction", "unit": { "kind": "file", "path": "crates/aicortex-gate/src/rules.rs" } } - extends
{ "nature": "additive", "spec": "013-write-gate-and-redaction", "unit": { "kind": "file", "path": "crates/aicortex-gate/src/secrets.rs" } } - extends
{ "nature": "additive", "spec": "013-write-gate-and-redaction", "unit": { "kind": "file", "path": "crates/aicortex-gate/Cargo.toml" } } - extends
{ "nature": "additive", "spec": "013-write-gate-and-redaction", "unit": { "kind": "file", "path": "crates/aicortex-gate/testdata/corpus/" } } - extends
{ "nature": "additive", "spec": "013-write-gate-and-redaction", "unit": { "kind": "file", "path": "crates/aicortex-gate/tests/gate.rs" } } - extends
{ "nature": "additive", "spec": "010-chassis-adoption-and-workspace", "unit": { "anchor": "workspace.dependencies", "file": "Cargo.toml", "kind": "section" } }
Source headings
- 047: Shared secret detector convergence
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 What moves and what stays
- 3.2 Consumption
- 3.3 Prerequisite
- 4. Functional requirements
- 5. Acceptance criteria
- 6. Out of scope
- 7. Resolved decisions
- 8. Follow-ups and open questions
- 9. Obligations
- Verification
Frozen anchors
No frozen anchors declared.