Launch second-wave implementation workplans
This commit is contained in:
parent
1bc78cccfa
commit
ffbd4178ce
2 changed files with 16 additions and 7 deletions
|
|
@ -29,8 +29,8 @@
|
|||
| task | RAILIANCE-WP-0019-T03 | done | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T04 | done | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T05 | done | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T06 | progress | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T07 | progress | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T06 | done | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T07 | done | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T08 | progress | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T09 | progress | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
| task | RAILIANCE-WP-0019-T10 | progress | — | workplans/RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md |
|
||||
|
|
|
|||
|
|
@ -281,7 +281,7 @@ treated as implementation completion.
|
|||
|
||||
```task
|
||||
id: RAILIANCE-WP-0019-T06
|
||||
status: progress
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "18fe6f04-f8c5-451b-8e3f-38c19f05f682"
|
||||
```
|
||||
|
|
@ -307,11 +307,16 @@ Acceptance:
|
|||
must separate source-repo, package, derived-rail, reef admission, Fabric
|
||||
compatibility, identity/custody, and S2 runtime installation responsibilities.
|
||||
|
||||
2026-07-26: Opened and State Hub registered repo-local execution work in
|
||||
`rail-kubernetes`, `rail-knative`, `rapp-qonto`, `reef-railiance`,
|
||||
`railiance-fabric`, `qonto-assistant`, and `key-cape`. The two new repos were
|
||||
reconciled with their existing Forgejo bootstrap commits and pushed.
|
||||
|
||||
## T07 - Version the rail-neutral workload and compatibility contract
|
||||
|
||||
```task
|
||||
id: RAILIANCE-WP-0019-T07
|
||||
status: progress
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "5b5f2d41-2860-44ee-a8b6-8b9e1d32854f"
|
||||
```
|
||||
|
|
@ -327,6 +332,10 @@ Acceptance:
|
|||
substrate capabilities
|
||||
- Kubernetes remains the default binding for platform workloads
|
||||
|
||||
2026-07-26: `rail-kubernetes` now publishes base contract `1.0.0`, common
|
||||
workload, rail-binding, and derived-rail schemas, a Kubernetes-default example,
|
||||
and an offline validator. `rail-knative` and `rapp-qonto` pass that validator.
|
||||
|
||||
## T08 - Establish reef admission evidence and mixed-rail split triggers
|
||||
|
||||
```task
|
||||
|
|
@ -401,11 +410,11 @@ Acceptance:
|
|||
- [x] derived-rail composition and non-duplication are decided
|
||||
- [x] reef readiness and mixed-rail split rules are decided
|
||||
- [x] Qonto end-to-end failure, rollback, and security boundaries are written
|
||||
- [ ] common and rail-binding schemas are implemented
|
||||
- [ ] repo-local implementation workplans are registered and active
|
||||
- [x] common and rail-binding schemas are implemented
|
||||
- [x] repo-local implementation workplans are registered and active
|
||||
- [ ] conformance and credential-routing paths are agent-executable
|
||||
- [x] second-wave repo bootstrap order is defined
|
||||
- [ ] repo-local implementation workplans exist before implementation begins
|
||||
- [x] repo-local implementation workplans exist before implementation begins
|
||||
|
||||
## Notes
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue