Enforce bounded operation guardrails
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a028de-e2c8-7732-8521-46a7fc5db82f
This commit is contained in:
parent
c384f60530
commit
26934e25b9
51 changed files with 1843 additions and 472 deletions
|
|
@ -4,7 +4,7 @@ type: workplan
|
|||
title: "Make the execution boundary enforceable and the review contract truthful"
|
||||
domain: infotech
|
||||
repo: activity-core
|
||||
status: ready
|
||||
status: active
|
||||
owner: codex
|
||||
topic_slug: activity-core
|
||||
priority: high
|
||||
|
|
@ -92,7 +92,7 @@ and enforce it in definition admission and workflow structure. At completion:
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T01
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ without making activity-core a general executor.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T02
|
||||
status: wait
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -145,7 +145,7 @@ query without an explicit reviewed registry entry and tests prove each refusal.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T03
|
||||
status: wait
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -170,7 +170,7 @@ operations pass unit, retry, redaction, and workflow-order tests.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T04
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
```
|
||||
|
||||
|
|
@ -192,7 +192,7 @@ audit claim.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T05
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
```
|
||||
|
||||
|
|
@ -217,7 +217,7 @@ migration path are recorded in ADR-003 or a successor ADR.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T06
|
||||
status: wait
|
||||
status: done
|
||||
priority: medium
|
||||
```
|
||||
|
||||
|
|
@ -238,7 +238,7 @@ not close the live acceptance item.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T07
|
||||
status: todo
|
||||
status: done
|
||||
priority: low
|
||||
```
|
||||
|
||||
|
|
@ -262,7 +262,7 @@ activity-core is a general task executor.
|
|||
|
||||
```task
|
||||
id: ACTIVITY-WP-0035-T08
|
||||
status: wait
|
||||
status: progress
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -281,15 +281,32 @@ Depends on T02–T07 as applicable.
|
|||
|
||||
## Acceptance
|
||||
|
||||
- [ ] `INTENT.md` explicitly distinguishes work-item lifecycle from ops-run delivery state
|
||||
- [ ] The bounded-operation exception is governed by a reviewed contract, not convention
|
||||
- [ ] Definition sync refuses unknown or incomplete mutating operation declarations
|
||||
- [ ] Context resolvers are read-only; mutations run in an explicit bounded-operation phase
|
||||
- [ ] Instruction audit wording matches persisted evidence and raw sensitive payloads remain excluded
|
||||
- [ ] `review_required` has truthful, tested hold/release or advisory-only semantics
|
||||
- [ ] Misleading executor/CRUD/README surfaces are removed or precisely qualified
|
||||
- [x] `INTENT.md` explicitly distinguishes work-item lifecycle from ops-run delivery state
|
||||
- [x] The bounded-operation exception is governed by a reviewed contract, not convention
|
||||
- [x] Definition sync refuses unknown or incomplete mutating operation declarations
|
||||
- [x] Context resolvers are read-only; mutations run in an explicit bounded-operation phase
|
||||
- [x] Instruction audit wording matches persisted evidence and raw sensitive payloads remain excluded
|
||||
- [x] `review_required` has truthful, tested hold/release or advisory-only semantics
|
||||
- [x] Misleading executor/CRUD/README surfaces are removed or precisely qualified
|
||||
- [ ] Full tests pass and production rollout preserves current schedules and evidence
|
||||
|
||||
## Implementation evidence — 2026-08-23
|
||||
|
||||
- ACT-ADR-007 accepted and recorded as State Hub decision
|
||||
`2b1f0c01-1d6f-4fdc-b3e7-537ce0a0a1f8`.
|
||||
- Strict parsing admitted all 12 checked-in definitions; refusal tests cover
|
||||
unknown shell queries, missing operation declarations, arbitrary script
|
||||
paths, missing evidence, target/limit bounds, and multiple mutations.
|
||||
- Full suite: `453 passed, 1 skipped` in 139.62 seconds; subsequent API
|
||||
admission/render-focused suite: `40 passed`.
|
||||
- PostgreSQL migration `0008 → 0009 → 0008 → 0009` passed in an isolated
|
||||
PostgreSQL 16 database. The final state has no `task_instances` table and has
|
||||
`task_spawn_log.review_advisory`.
|
||||
- Production removal inventory before migration: zero `task_instances`, no
|
||||
worker feature flag, and zero Temporal `TaskExecutorWorkflow` executions.
|
||||
- Compatibility detail is retained in
|
||||
`history/2026-08-23-bounded-operation-compatibility-report.md`.
|
||||
|
||||
## Gap disposition
|
||||
|
||||
| 2026-08-23 gap | This workplan |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue