Bind knowledge retrieval to sealed bytes and invalidate changed releases
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a10238-7ecc-78e2-903d-075f50e913cc
This commit is contained in:
parent
416f9919c5
commit
d0bf65e964
16 changed files with 335 additions and 40 deletions
|
|
@ -34,7 +34,7 @@ requested by this package.
|
|||
Actual resume/compaction behavior and governed glas-harness sessions remain
|
||||
separate proofs. The reload code is tested, and fresh sessions are exercised;
|
||||
neither proves what an actual provider preserves after compaction. Honor the
|
||||
blocked/unverified owner profile states. CUST-WP-0073 and GLAS-WP-0008 already
|
||||
blocked/unverified owner profile states. CUST-WP-0073 and GLAS-WP-0012 already
|
||||
own credential/isolation/readiness concerns; this package does not close them.
|
||||
|
||||
The four real-repository read-only pilot reports cover doctrine, access,
|
||||
|
|
@ -71,3 +71,14 @@ routes withdrawn credential guidance to its source owner/ops-warden and missing
|
|||
events to their emitting source owner. The completion audit preserves failed
|
||||
full runs, bounded retry passes and unresolved owner/provider/independent gates.
|
||||
EMERGENT-WP-0002 is blocked; this review package does not claim adoption.
|
||||
|
||||
|
||||
## Owner review and corrected release — 0.2.2
|
||||
|
||||
The current unsigned draft binds 0.2.2, digest
|
||||
`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`.
|
||||
`docs/evidence/2026-10-03-owner-reviews-and-022-fixes.md` indexes the owner
|
||||
reviews, concrete publication/distribution proposal, Whitehat findings and
|
||||
local fixes. Technical reviews retain 0.2.1 pins; they are not human adoption.
|
||||
Whitehat close-out and independence acceptance remain incomplete after its
|
||||
platform stop. Provider/continuity, pilot and rollout gates remain live.
|
||||
|
|
|
|||
|
|
@ -52,9 +52,9 @@ Release **0.2.0 (pilot)** adds `decisions` and `runbooks` cards, startup discove
|
|||
and revision-pinned owner contracts/code. There are 14 cards, 24 owners and
|
||||
69 source files. This is file review, not live capability verification.
|
||||
|
||||
The current pilot is **0.2.1**, which clarifies withdrawn-procedure refresh and
|
||||
Release **0.2.1**, which clarifies withdrawn-procedure refresh and
|
||||
missing-event reconciliation recipients after provider evaluation. The unsigned
|
||||
adoption draft binds this corrected release. Exact-release reports and remaining
|
||||
adoption draft always binds the current corrected release. Exact-release reports and remaining
|
||||
closure gates are indexed in `docs/evidence/2026-10-03-closure-attempt.md`.
|
||||
|
||||
- `runbooks/security-orientation/pack.yaml` is a native v0.2 pack owned here. It
|
||||
|
|
@ -118,3 +118,10 @@ A UI session is not started or exposed by this integration.
|
|||
Authoritative references: the pinned `informed-decision` and `runbook-tutorials`
|
||||
entries in `knowledge/sources.yaml`; related contracts in
|
||||
`docs/operational-contracts.md` and owner map in `docs/netkingdom-integration-map.md`.
|
||||
|
||||
|
||||
Current pilot **0.2.2** invalidates loaded knowledge after local release changes
|
||||
and serves the exact validated card bytes, addressing Whitehat findings
|
||||
WH-KNOW-001/002. Its unsigned draft is freshly rebuilt. The owner-reviewed Glas
|
||||
source correction preserves absent observed model metadata as unknown.
|
||||
Neither change resolves the existing human adoption or native continuity gates.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"kind": "informed-decision.memo-intake",
|
||||
"version": 1,
|
||||
"idempotency_key": "emergent-profile-d8ef41bacd2c6551ae3b87628004a5df6943928be1c93eb01e09efc6ad782767",
|
||||
"idempotency_key": "emergent-profile-19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c",
|
||||
"memo_class": "knowledge-profile",
|
||||
"review_group": "net-kingdom-admins",
|
||||
"drafted_by": "codex@emergent-security (asserted)",
|
||||
|
|
@ -14,15 +14,15 @@
|
|||
"principal": "emergent-security",
|
||||
"purpose": "Accept only the non-normative knowledge profile boundary",
|
||||
"target": {
|
||||
"id": "emergent-security:knowledge:0.2.1:d8ef41bacd2c6551ae3b87628004a5df6943928be1c93eb01e09efc6ad782767",
|
||||
"id": "emergent-security:knowledge:0.2.2:19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c",
|
||||
"type": "knowledge-profile",
|
||||
"system": "emergent-security"
|
||||
}
|
||||
},
|
||||
"memo": {
|
||||
"id": "emergent-profile-adoption-0-2-1",
|
||||
"id": "emergent-profile-adoption-0-2-2",
|
||||
"version": 1,
|
||||
"question": "Accept Emergent Security knowledge 0.2.1 as a non-normative NetKingdom agent orientation profile?",
|
||||
"question": "Accept Emergent Security knowledge 0.2.2 as a non-normative NetKingdom agent orientation profile?",
|
||||
"requested_act": "approve",
|
||||
"binding_level": "organizational",
|
||||
"brief": "Accept only the orientation boundary of this exact release; operational authority and remaining review gates stay with their owners.",
|
||||
|
|
@ -35,7 +35,7 @@
|
|||
"identifiers": []
|
||||
},
|
||||
"target": {
|
||||
"id": "emergent-security:knowledge:0.2.1:d8ef41bacd2c6551ae3b87628004a5df6943928be1c93eb01e09efc6ad782767",
|
||||
"id": "emergent-security:knowledge:0.2.2:19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c",
|
||||
"kind": "knowledge-profile",
|
||||
"label": "Non-normative security orientation",
|
||||
"environment": "rehearsal",
|
||||
|
|
@ -49,7 +49,7 @@
|
|||
{
|
||||
"item_id": "emergent-profile-packet",
|
||||
"label": "Profile boundary and limitations",
|
||||
"hash": "sha256:f06b74051ac404dbc82494da4f723939e104787640e7bbdf32c049f609228c0a"
|
||||
"hash": "sha256:3c598ac0754c0fe6d6eab6e5c6910f97f8798adc35eeda4fed22c4ecd0c2f66b"
|
||||
}
|
||||
],
|
||||
"highlights": [
|
||||
|
|
@ -76,7 +76,7 @@
|
|||
{
|
||||
"item_id": "emergent-profile-packet",
|
||||
"media_type": "text/markdown",
|
||||
"content": "# Knowledge profile adoption request\n\nAdopt Emergent Security knowledge 0.2.1, release digest d8ef41bacd2c6551ae3b87628004a5df6943928be1c93eb01e09efc6ad782767, as a\nnon-normative orientation profile for coding agents in NetKingdom.\n\nThe profile points to existing owners, withholds stale guidance, and separates\nhuman decisions, runtime approvals, PDP decisions, credentials and procedure\nrecords. This asks only to accept that orientation boundary. It does not amend\nowner contracts or authorize operational effects, autonomous execution, root,\ncredential changes or fleet rollout.\n\nAlternatives: return for wording/source corrections; decline this profile;\naccept this exact orientation boundary with the documented evidence limits.\nChanging the reviewed package requires a new review, not reuse of this answer.\n\nEvidence: knowledge/sources.yaml; docs/decision-runbook-integration.md;\ndocs/operational-contracts.md; docs/adoption-review.md; docs/evidence/.\nEarlier provider reports concern release 0.1.1. New integration evidence is\nseparately scoped; no independent review or full Grok validation is claimed.\nActual compaction/harness proof and wider adoption remain open in EMERGENT-WP-0002.\n\nThe draft is unsubmitted. The proposed memo class and review group must be\nconfirmed by the owner; a synthetic test grant proves format only. INFD-WP-0005\nintake rollout remains unfinished. This draft resolves no Statehub decision.\n"
|
||||
"content": "# Knowledge profile adoption request\n\nAdopt Emergent Security knowledge 0.2.2, release digest 19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c, as a\nnon-normative orientation profile for coding agents in NetKingdom.\n\nThe profile points to existing owners, withholds stale guidance, and separates\nhuman decisions, runtime approvals, PDP decisions, credentials and procedure\nrecords. This asks only to accept that orientation boundary. It does not amend\nowner contracts or authorize operational effects, autonomous execution, root,\ncredential changes or fleet rollout.\n\nAlternatives: return for wording/source corrections; decline this profile;\naccept this exact orientation boundary with the documented evidence limits.\nChanging the reviewed package requires a new review, not reuse of this answer.\n\nEvidence: knowledge/sources.yaml; docs/decision-runbook-integration.md;\ndocs/operational-contracts.md; docs/adoption-review.md; docs/evidence/.\nEarlier provider reports and owner reviews retain their original release pins.\nWhitehat's separately authored offline 0.2.1 review found loaded-package binding\nand lifecycle gaps; 0.2.2 addresses them with local regressions. Review close-out\nand clean independent acceptance remain incomplete. No full Grok validation is claimed.\nActual compaction/harness proof and wider adoption remain open in EMERGENT-WP-0002.\n\nThe draft is unsubmitted. The proposed memo class and review group must be\nconfirmed by the owner; a synthetic test grant proves format only. INFD-WP-0005\nintake rollout remains unfinished. This draft resolves no Statehub decision.\n"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
|
|||
33
docs/evidence/2026-10-03-022-package-check.json
Normal file
33
docs/evidence/2026-10-03-022-package-check.json
Normal file
|
|
@ -0,0 +1,33 @@
|
|||
{
|
||||
"schema": "emergent.knowledge-check.v1",
|
||||
"version": "0.2.2",
|
||||
"package_digest": "19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c",
|
||||
"sources": {
|
||||
"net-kingdom": "verified-files",
|
||||
"gate-house": "verified-files",
|
||||
"ops-warden": "verified-files",
|
||||
"ops-mason": "verified-files",
|
||||
"access-engine": "verified-files",
|
||||
"security-canon": "verified-files",
|
||||
"user-engine": "verified-files",
|
||||
"tenant-engine": "verified-files",
|
||||
"zone-engine": "verified-files",
|
||||
"whitehat-security": "verified-files",
|
||||
"kings-guard": "verified-files",
|
||||
"secrets-engine": "verified-files",
|
||||
"key-cape": "verified-files",
|
||||
"approval-engine": "verified-files",
|
||||
"informed-decision": "verified-files",
|
||||
"audit-core": "verified-files",
|
||||
"risk-nexus": "verified-files",
|
||||
"info-tech-canon": "verified-files",
|
||||
"ops-bridge": "verified-files",
|
||||
"railiance-master": "verified-files",
|
||||
"glas-harness": "verified-files",
|
||||
"the-custodian": "verified-files",
|
||||
"emergent-security": "verified-files",
|
||||
"runbook-tutorials": "verified-files"
|
||||
},
|
||||
"live_state_verified": false,
|
||||
"ok": true
|
||||
}
|
||||
93
docs/evidence/2026-10-03-owner-reviews-and-022-fixes.md
Normal file
93
docs/evidence/2026-10-03-owner-reviews-and-022-fixes.md
Normal file
|
|
@ -0,0 +1,93 @@
|
|||
# Owner reviews and loaded-package consistency fixes — 2026-10-03
|
||||
|
||||
Current pilot: **0.2.2**, manifest digest
|
||||
`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`.
|
||||
All 24 inventoried source owners verify as files; startup remains 5,091 bytes.
|
||||
File checks do not prove deployment, permission, provider readiness or adoption.
|
||||
|
||||
## Separately scoped owner evidence
|
||||
|
||||
| Owner | Review artifact / live record | Observed disposition |
|
||||
| --- | --- | --- |
|
||||
| gate-house | `docs/conformance/2026-10-03-emergent-knowledge-021-review.md`; GH-WP-ADHOC-2026-10-03-T02; pushed `755c36ae19c3789365d8f6405158730365da3572` | No blocking doctrine conflict in the non-normative profile; human adoption/publication remain open |
|
||||
| net-kingdom | `docs/evidence/2026-10-03-emergent-knowledge-021-review.md`; NK-WP-ADHOC-2026-10-03-T01; pushed `9e3ad860d61e0b6a3a23d9c1a54235e1d73d3b76` | Accurate owner boundaries; documentary feedback on retained pilot; publication pointer proposed after gates |
|
||||
| security-canon | `docs/emergent-knowledge-021-review.md`; SECURITY-WP-ADHOC-2026-10-03-T01; pushed `5a67d60184025cc0292b714f5da43ef5f0b6a588` | No blocking mode/scope vocabulary conflict; optional principal-type source clarification remains SECURITY-IN-0001 |
|
||||
| access-engine (flex-auth) | `docs/evidence/2026-10-03-emergent-profile-boundary-review.md`; pushed `d7f85a7dde28a120a635b748aa64805a2f7fdf84` | Scoped technical acceptance of orientation/PDP distinction, binding/approval/fact boundaries; no live authorization |
|
||||
| glas-harness | `docs/evidence/2026-10-03-emergent-session-readiness-review.md`; GLAS-WP-0012-T04; pushed `5ce4f38aedfd27cc783131f18480df02e2951514` | Native continuity is not currently supplied by the lifecycle contract; configured model pins cannot substitute for observed model metadata |
|
||||
| the-custodian | `docs/emergent-knowledge-distribution-draft.md`; CUST-WP-0073-T04; pushed `c4558d4d10b58946c1534c7f5ccaef5ab6210890` | Concrete distribution/maintenance proposal, unaccepted and unpublished; native identity/readiness gates remain |
|
||||
| whitehat-security | `evidence/2026-10-03-emergent-021-offline-review.md` and `.json`; WHITEHAT-WP-0009 | Nine separately authored offline probes: seven bounded passes, two findings; review close-out interrupted |
|
||||
|
||||
Paths above are relative to their owner repository. Reviews retain original
|
||||
0.2.1 digest/commit and independence limits. They are agent-authored technical
|
||||
reviews, not authenticated human decisions or institutional assent. Renewed
|
||||
exact-release evidence is required after changed source/runtime artifacts.
|
||||
Gate House/NetKingdom/SecurityCanon worker reported primary reconciliation with
|
||||
matching pushed and derived commits; runtime owner sync receipts are tracked by
|
||||
that worker. No pending publication proposal is treated as accepted doctrine.
|
||||
|
||||
Proposed ownership division is now concrete: Emergent maintains/seals the bundle;
|
||||
NetKingdom publishes the estate profile pointer; Gate House owns teaching;
|
||||
SecurityCanon owns imported vocabulary; Glas owns native session delivery and
|
||||
proof; the Custodian coordinates reach after accepted rollout gates. The
|
||||
existing adoption decision remains `d20a9750-2b29-534e-8227-fb866581a6ca`.
|
||||
|
||||
## Whitehat findings and local remediation
|
||||
|
||||
WH-KNOW-001: modifying a card after `Knowledge()` construction previously
|
||||
returned unsealed bytes under the original receipt digest. WH-KNOW-002: an
|
||||
already loaded source lifecycle remained active after withdrawal/reseal while
|
||||
fresh construction correctly withheld it. Both are copied-bundle library
|
||||
consistency findings; neither establishes runtime permission bypass or a live
|
||||
attack. Detailed prerequisites and limits remain in Whitehat's original report.
|
||||
|
||||
The five regression cases were introduced before the implementation fix and
|
||||
failed against the previous runtime: post-load card mutation; resealed withdrawal
|
||||
on retrieval, check and public source-status; and changing a card after its byte
|
||||
read to test that returned content is exactly the validated content.
|
||||
|
||||
The runtime now reads/parses metadata from the same sealed byte snapshot,
|
||||
revalidates the original release digest and all package files on each public
|
||||
retrieval/check/source-status operation, detects a changed seal before and after
|
||||
bundle reads, and requires explicit reload of a newly reviewed bundle. Returned
|
||||
cards decode the exact bytes just hashed, with no second content-file read.
|
||||
An unsealed file update fails closed. Offline bundles cannot discover owner
|
||||
withdrawals that have not been delivered; documented freshness limits remain.
|
||||
|
||||
Local verification: **341 tests pass**, including nine real owner-contract tests;
|
||||
focused knowledge suite **38 pass**. Seal, exact-release adoption-draft freshness,
|
||||
and all 24 source-file checks pass. Wheel and source archive build; unpacked
|
||||
wheel retrieval loads the corrected runtime and 0.2.2 seal, returning the expected
|
||||
offline snapshot and startup size. The draft packet was rebuilt and owner-format
|
||||
checks rerun after its explanatory text changed. None is independent retest or
|
||||
institutional acceptance of remediation.
|
||||
|
||||
## Source-change handling and evidence limits
|
||||
|
||||
Glas fixed configured-pin fallback in its gateway/adapters and documented that
|
||||
only a rein/provider report supplies `resolved_model`; missing observations stay
|
||||
null, and an alias is not an exact revision or conversation ID. Its worker reports
|
||||
139 deterministic tests pass. The append to inventoried harness-contract.md
|
||||
caused our old source check to return `changed`, as intended. After inspecting
|
||||
the appendix and matching all three inventoried files against the actual owner
|
||||
commit, we re-pinned Glas to the pushed revision above and resealed 0.2.2.
|
||||
No other owner source was silently refreshed. GLAS-WP-0008 is finished;
|
||||
GLAS-WP-0012 owns remaining acceptance rather than the completed historical plan.
|
||||
|
||||
Whitehat's separate review of retained provider answers accepts Codex 28/28;
|
||||
Claude is **26/28** under its recipient rubric (zones routes to PDP instead of
|
||||
capability owner; model-switch routes to package publisher). The implementing
|
||||
session's earlier 27/28 report stays unchanged; neither is relabeled as 0.2.2.
|
||||
No unsafe effect recommendation was observed in those retained answers.
|
||||
|
||||
The platform's cybersecurity-risk review stopped the Whitehat worker after its
|
||||
findings/reproductions were saved and delivered. WHITEHAT-WP-0009-T03 close-out,
|
||||
owner sync and any clean independent acceptance remain incomplete. The saved
|
||||
report clearly says the reviewer shares parent session/model/workspace and is
|
||||
not a separately authenticated Whitehat principal. This work does not bypass
|
||||
that stop or label root-authored regressions as independent validation.
|
||||
|
||||
Remaining required work stays live in EMERGENT-WP-0002 T02/T05/T07/T08/T09/T10,
|
||||
WHITEHAT-WP-0009-T03, GLAS-WP-0012 and CUST-WP-0073. Provider evaluation and
|
||||
pilot/admission owner feedback continue in their assigned repository workers.
|
||||
No DoD-Ok, submitted adoption, fleet notice, credential operation, blocked
|
||||
profile activation or live production change is claimed.
|
||||
|
|
@ -66,6 +66,13 @@ current owner's authorization path.
|
|||
|
||||
## Refresh ownership
|
||||
|
||||
From 0.2.2, each retrieval, check and public source-status call revalidates the
|
||||
loaded release seal and package files. Returned cards use the exact bytes
|
||||
validated against that seal. A changed seal invalidates the loaded object:
|
||||
explicitly reload the reviewed bundle rather than silently following an update.
|
||||
Unsealed file changes fail closed. This detects local bundle changes; an offline
|
||||
bundle still cannot discover an upstream withdrawal it has not received.
|
||||
|
||||
Emergent Security maintains the package and tests. Every source remains owned
|
||||
by its repository; gate-house/net-kingdom adoption and publication review are
|
||||
tracked in EMERGENT-WP-0002-T02/T09, not presumed accepted. Review at least every
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ All references are pinned; `knowledge/sources.yaml` also records file hashes and
|
|||
| info-tech-canon | shared-semantics | [README.md](https://forgejo.coulomb.social/coulomb/info-tech-canon/src/commit/b30c831b387b11b41b2a4206e516fac65b84c29f/README.md) |
|
||||
| ops-bridge | transport | [README.txt](https://forgejo.coulomb.social/coulomb/ops-bridge/src/commit/190ef1e188e12c606f1359325fd9fdd1dbef29e2/README.txt); [INTENT.md](https://forgejo.coulomb.social/coulomb/ops-bridge/src/commit/190ef1e188e12c606f1359325fd9fdd1dbef29e2/INTENT.md) |
|
||||
| railiance-master | workload-operations | [README.md](https://forgejo.coulomb.social/coulomb/railiance-master/src/commit/a61b31396f0936ddd302b27a5222046240e413b2/README.md); [INTENT.md](https://forgejo.coulomb.social/coulomb/railiance-master/src/commit/a61b31396f0936ddd302b27a5222046240e413b2/INTENT.md) |
|
||||
| glas-harness | session-execution | [README.md](https://forgejo.coulomb.social/coulomb/glas-harness/src/commit/dc49415c9f7c62a4d16e29e0ffa7be00eb002c28/README.md); [docs/harness-contract.md](https://forgejo.coulomb.social/coulomb/glas-harness/src/commit/dc49415c9f7c62a4d16e29e0ffa7be00eb002c28/docs/harness-contract.md); [docs/execution-profiles.md](https://forgejo.coulomb.social/coulomb/glas-harness/src/commit/dc49415c9f7c62a4d16e29e0ffa7be00eb002c28/docs/execution-profiles.md) |
|
||||
| glas-harness | session-execution | [README.md](https://forgejo.coulomb.social/coulomb/glas-harness/src/commit/5ce4f38aedfd27cc783131f18480df02e2951514/README.md); [docs/harness-contract.md](https://forgejo.coulomb.social/coulomb/glas-harness/src/commit/5ce4f38aedfd27cc783131f18480df02e2951514/docs/harness-contract.md); [docs/execution-profiles.md](https://forgejo.coulomb.social/coulomb/glas-harness/src/commit/5ce4f38aedfd27cc783131f18480df02e2951514/docs/execution-profiles.md) |
|
||||
| the-custodian | estate-orientation | [docs/agent-environment-orientation.md](https://forgejo.coulomb.social/coulomb/the-custodian/src/commit/f303bdaff1a7f3f2305a375a3b5870cb0262e70c/docs/agent-environment-orientation.md); [docs/agent-autonomy-decision.md](https://forgejo.coulomb.social/coulomb/the-custodian/src/commit/f303bdaff1a7f3f2305a375a3b5870cb0262e70c/docs/agent-autonomy-decision.md); [docs/security-close-down-checklist.md](https://forgejo.coulomb.social/coulomb/the-custodian/src/commit/f303bdaff1a7f3f2305a375a3b5870cb0262e70c/docs/security-close-down-checklist.md) |
|
||||
| emergent-security | offline-reference | [specs/emergent-security-0.8.md](https://forgejo.coulomb.social/coulomb/emergent-security/src/commit/caa7da2397ff860dba4de2824da998ed8c045ef2/specs/emergent-security-0.8.md); [envelopes/default-envelope.yaml](https://forgejo.coulomb.social/coulomb/emergent-security/src/commit/caa7da2397ff860dba4de2824da998ed8c045ef2/envelopes/default-envelope.yaml) |
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ All references are pinned; `knowledge/sources.yaml` also records file hashes and
|
|||
- tenant-engine SCOPE contains old gaps beside newer shipped entries. TEN-WP-0012 tracks outstanding external custody/canon dependencies; treat runtime readiness separately.
|
||||
- access-engine decision-record documentation contains old unsigned-channel prose beside newer signature fields; actual consumer authentication/enforcement requires current owner proof.
|
||||
- the-custodian CUST-WP-0073 tracks agent credential separation. Loading this knowledge does not close that work.
|
||||
- glas-harness GLAS-WP-0008 separates operational readiness from profile selection; blocked/unverified profiles remain so.
|
||||
- glas-harness GLAS-WP-0008 is finished: operational readiness is separate from profile selection. GLAS-WP-0012 owns remaining runtime/provider acceptance and continuity proof; blocked/unverified profiles remain so.
|
||||
- gate-house GH-WP-0004 holds layer-declaration work. This repo declares its own boundary; it does not declare conformance on behalf of another owner.
|
||||
- OpenBao is referenced through secrets-engine and the net-kingdom infrastructure boundary; it is not a new repository or credential route owned here.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue