architecture: accept prospective notification delivery
This commit was merged in pull request #8.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# First external operation proposal
|
||||
|
||||
Status: **PROPOSED — NOT ACCEPTED**
|
||||
Status: **ACCEPTED by ADR-0005**
|
||||
|
||||
Task: `ARCH-000005`, revision 1
|
||||
|
||||
@@ -12,7 +12,7 @@ Choose the smallest useful real-world operation that exercises Domovoy's existin
|
||||
|
||||
`Creator session → owner validation → live Work justification → Capability binding revision → Authority validation → durable Commit → isolated Executor → external receipt → durable attempt/outcome → read-only reconciliation`
|
||||
|
||||
This proposal changes no runtime, contract, schema, architecture authority, credential, endpoint, or deployment state. Its Tier E task packet selects itself in `dev/ACTIVE_TASK.json` only so fail-closed promotion CI validates the proposal's exact diff.
|
||||
The proposal task changed no runtime, contract, schema, credential, endpoint, or deployment state. Its recommendation and the local Windows display channel were subsequently accepted by `ADR-0005` under task `ARCH-000006`.
|
||||
|
||||
## Current gap
|
||||
|
||||
@@ -141,11 +141,6 @@ The endpoint origin and paths come only from the validated binding. Redirects ar
|
||||
6. Add the explicit Creator confirmation flow and action-history rendering.
|
||||
7. Configure one concrete compatible destination, generate its credential outside Git, deploy on `docker-prod`, and run exact-artifact production smoke.
|
||||
|
||||
## Decision still required
|
||||
## Resolution
|
||||
|
||||
Implementation is `BLOCKED_BY_SPEC_GAP` until both are explicitly accepted:
|
||||
|
||||
1. the typed operation and safety protocol in this proposal;
|
||||
2. one concrete destination base URL that implements the receipt protocol, including where the resulting notification is ultimately shown to the Creator.
|
||||
|
||||
No credential should be generated before that destination exists.
|
||||
`ADR-0005` accepts this typed operation and protocol. The first compatible receiver will run on `docker-prod` behind the existing `https://assistent.cin.su` origin, and a separately authorized local Windows agent will show accepted receipts to the Creator. Receiver acceptance is the external Commit outcome; operating-system display and human reading are not.
|
||||
|
||||
Reference in New Issue
Block a user