Skip to content

feat: establish identity, delegation and task admission foundation - #212

Closed
bordumb wants to merge 34 commits into
codex/ap-spec-071from
codex/identity-authority-foundation
Closed

bordumb wants to merge 34 commits into
codex/ap-spec-071from
codex/identity-authority-foundation

Conversation

@bordumb

@bordumb bordumb commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Behavior

This draft implements AP-SPEC-073's identity, delegated authority and admission foundation within the existing monorepo. A signed engagement separates initiation from exact human approval and binds its partition, participant instances, delegation depth and channels. Native root/child enrollment is persisted with the task journal and required for resource operations.

  • Resource authority is exclusive to the task, partition and installed recipe. Rust, Python and TypeScript authoring support the explicit audience; operator trust must admit it independently.
  • Reads, disclosures and writes share bounded ancestor accounting. Revocation retains operation charges and immutable participant attribution.
  • Disclosure authenticates the enrolled recipient and consumes a durable entry permit binding the exact operation, bytes and commitment key. Schema-2 acknowledgements bind the complete participant tuple and remain recordable after revocation.
  • Exact write approval includes the enrolled writer, partition, enrollment and instance. Agent A cannot reuse human approval of B merely by signing the same action payload. Create/populate lineage preserves the writer; bounded-upfront writes remain root-only.
  • Task review returns Rust's exact intent and canonical confirmation arguments. Python presentation consumes that intent instead of independently constructing the request commitment. A native enrolled-child fixture and Python consumer compare signing bytes.
  • Task writes reverify the native command before a durable entry grant under the same task lock as revocation. A noncloneable permit carries the exact closed request. Revocation before the grant denies it; a grant before revocation may finish or become unknown. Dropping the permit or restarting cannot obtain a second grant or refund capacity. The entry grant is distinct from provider receipt, which remains an attempt-journal fact.

Direct prelaunch cutovers: task schema 4, installation schema 5, task journal schema 13, root/tree schema 2, disclosure challenge/ACK schema 2, and exact confirmation/effect-plan tools v2. No old-state decoder or dual execution path is added. Provider semantics remain data-only recipes.

Remaining program

The goal is all M0–M4 and F01–F16; none is declared complete. The final-card/operator trust and native bootstrap workflow, isolated machine → A → B demonstration, provider-read entry ordering, complete native evidence/approval freshness at later entry, identity recovery, whole-store rollback protection, full task activity/audit, native enforcement and federation remain open. Current Google workbench orchestration still needs its task-scoped authority/bootstrap cutover.

The installed child scenario exercises native company → machine → A → B enrollment, independent human approval, actual loopback PATCH and GET observation, and checks that the entry grant is durable at the provider socket. It is source-level coverage awaiting hosted execution; it does not qualify process isolation or a real provider.

Validation

Latest implementation: e4aac48de16617d1bba7252a790ee47577e03d23 (durable task write entry); 25f11876 adds native/Python signing fixture parity and repairs the preceding hosted lint failures.

  • Source-closure construction compiled the gateway tests and ran only the artifact constructor: 405 behavioral tests filtered out. Semantic inventory 413 was regenerated; formatting and diff checks passed. These are not behavioral acceptance.
  • Following the hosted failure, targeted gateway library/test Clippy passed for the 25f11876 repair. The subsequent entry changes await hosted lint and behavior checks.
  • New source tests cover deterministic and concurrent revocation/entry ordering, concurrent duplicate entry, substitutions, locked-time expiry, dropped permit/restart and corrupt/obsolete state. Python signing parity also awaits hosted execution.
  • CI 40608400324 is pinned to preceding 92ae3ce2, not this head. Preflight failed on three test-code Clippy diagnostics repaired in 25f11876; downstream behavior was skipped. Fast Lean feedback passed and the run is terminal. Full CI 40610522194 is now dispatched for e4aac48de16617d1bba7252a790ee47577e03d23; its results are pending.
  • Earlier CI 40594932593, on 5a71adc8, passed 356 gateway tests (26 ignored), compliance/dependencies/secrets, live PostgreSQL/OpenTofu/records API, Kani, authoritative Lean, reproduced translation and formal evidence. Its OpenAPI fixture failure was subsequently repaired through the maintained generator; eight targeted corpus tests passed. Those results do not qualify the later changes. The translated submit machine does not prove the new task-journal transition.

Stacked on AP071 (#211). Baseline 9b1fe3c202a202750704730aebc47e0585a24470 includes eight inherited commits beyond that branch's published 80443df9 head. Durable contracts and exact evidence gaps: docs/plans/0073-foundation-assessment.md and docs/plans/0073-engagement-participant-contract.md.

@bordumb bordumb changed the title feat(ap073): begin identity and delegated-authority foundation feat: establish identity, delegation and task admission foundation Oct 27, 2026
@bordumb
bordumb marked this pull request as ready for review November 7, 2026 23:40
@bordumb

bordumb commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

Closing in favor of #215

@bordumb bordumb closed this Nov 7, 2026
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