Add lifecycle registration and revisions with atomic packet uploads
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
parent
7ce1e589f7
commit
ee472acc87
10 changed files with 332 additions and 35 deletions
|
|
@ -23,8 +23,8 @@ or runtime configuration exposes these operations in this increment.
|
|||
|
||||
| Method | Contract |
|
||||
| --- | --- |
|
||||
| `register(context, memo, key=...)` | Version 1, no approval binding or seal; rejects ids already present in the memo store; returns durable event id |
|
||||
| `revise(context, memo, expected_version=..., summary=..., key=...)` | Exact current revision precondition and next version; nonempty change summary; returns durable event id |
|
||||
| `register(context, memo, key=..., documents=...)` | Version 1, no approval binding or seal; rejects ids already present in the memo store; returns durable event id |
|
||||
| `revise(context, memo, expected_version=..., summary=..., key=..., documents=...)` | Exact current revision precondition and next version; nonempty change summary; returns durable event id |
|
||||
| `annotate(context, memo_id, version, kind=..., body=..., key=...)` | Append source/evaluation/comment to an existing exact revision; returns durable event id |
|
||||
| `retrieve(tenant, memo_id, version=None)` | Retrieve current or historical memo only within its registered tenant |
|
||||
| `events(tenant, memo_id, after=0, limit=100)` | Ordered cursor page of attributed immutable events, maximum 100 |
|
||||
|
|
@ -93,3 +93,9 @@ legacy record enrollment, source fetching/retention, independent evidence delive
|
|||
and non-approval binding integration. T03 is started with this persistence slice;
|
||||
it is not complete. T04/T05 continue to own HTTP and UI exposure. Native runtime
|
||||
intake and admission remain with `INFD-WP-0005`.
|
||||
|
||||
Packet command extension: optional `documents` carries digest/media_type/base64
|
||||
content, verified and written in the same transaction as the memo/event. New
|
||||
registration requires packet bytes; revisions may retain their current packet's
|
||||
digests. The details and limits are in `LifecycleHTTPContract.md`. Idempotency
|
||||
digests for prior commands with no documents remain compatible.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue