Phase 5: Implement the independent authenticated capability service #371
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#380 Phase 5: Inject deterministic process crashes
erikinkinen/AES
#381 Phase 5: Emulate storage-prefix loss independently
erikinkinen/AES
#384 Phase 5: Generate three-way conformance tapes
erikinkinen/AES
#387 Phase 5: Implement service microbenchmark collection
erikinkinen/AES
#388 Phase 5: Define monitor availability and latency references
erikinkinen/AES
#395 Phase 5: Enforce inherited authenticated expiry
erikinkinen/AES
#372 Phase 5: Implement framed service transport
erikinkinen/AES
#375 Phase 5: Make service mutations idempotent
erikinkinen/AES
#373 Phase 5: Authenticate service tokens and protected reads
erikinkinen/AES
#374 Phase 5: Persist service authority transactions
erikinkinen/AES
#378 Phase 5: Run the standalone capability-service suite
erikinkinen/AES
#376 Phase 5: Publish service checkpoints atomically
erikinkinen/AES
#377 Phase 5: Export service monitoring and source identity
erikinkinen/AES
Reference
erikinkinen/AES#371
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan ID:
P5-20Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 9.8.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 7230.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
Provide an implementation independent of AES transition code.
Retained requirements
Child issues
Closure
This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted
not_applicablechild needs the signed route decision required by section 17.4.The service imports neither AES nor the reference interpreter and does not equate byte tokens with seL4 CSlots.
Execution and acceptance contract
Apply the governing semantic/data/statistical contracts in sections 3–5 and the relevant phase section, plus the section-11 checks applicable to this task. Section 17.4 defines the required acceptance evidence. Store the outcome and immutable prerequisite/input/output hashes at
artifacts/backlog/2.2.1/P5-20/acceptance.json.Only explicit dependency and parent-closure edges govern readiness; numbering adds no predecessor dependency. Checkboxes are work/acceptance items, not commit quotas. Keep implementation changes independently reviewable using the existing PR template. Execution, review and gate tasks close with their evidence/decision records and a PR only when tracked artifacts change.
An unsupported scientific effect is a valid result. Missing correctness validation, invalid inference or absent required review is not completion. Do not change endpoints, matrices, margins, inference rules or sample sizes outside the protocol change-control process.
Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.