Define the development provisioning-to-controller inbox profile #1

Open

ams-tech wants to merge 1 commit from codex/provisioning-inbox-profile into main

ams-tech commented

2026-09-11 19:12:52 -04:00

(Migrated from github.com)

The draft.1 wire schemas remain unchanged. The mapping preserves raw source state, source resource versions, immutable retries, development readiness restrictions, private evidence and the independent live-verification gate. The document also defines ownership and the controller's experimental read boundary for Flow.

Validation: all 19 contract tests pass, including the new fixture in the positive corpus. The controller's cross-repository rehearsal validates the producer output, checks retained evidence, handles duplicate delivery and survives restart.

Implementation: https://github.com/pd-codex/kaiba-controller. GitHub's integration returned HTTP 403 when creating a branch in PseudoDesign/kaiba-provisioning, so the tested upstream adapter is retained as integrations/provisioning-export.patch in the controller repository, with its pinned source baseline and checksum. Upstream landing remains pending access. This does not claim production readiness or completed live authority verification.

The shared contracts need a concrete first consumer anchored in the existing provisioning workflow. This change documents an observation-only integration and adds a ProvisioningRecord generated by the real control/audit services with simulated operation evidence. The draft.1 wire schemas remain unchanged. The mapping preserves raw source state, source resource versions, immutable retries, development readiness restrictions, private evidence and the independent live-verification gate. The document also defines ownership and the controller's experimental read boundary for Flow. Validation: all 19 contract tests pass, including the new fixture in the positive corpus. The controller's cross-repository rehearsal validates the producer output, checks retained evidence, handles duplicate delivery and survives restart. Implementation: https://github.com/pd-codex/kaiba-controller. GitHub's integration returned HTTP 403 when creating a branch in PseudoDesign/kaiba-provisioning, so the tested upstream adapter is retained as integrations/provisioning-export.patch in the controller repository, with its pinned source baseline and checksum. Upstream landing remains pending access. This does not claim production readiness or completed live authority verification.

This pull request has changes conflicting with the target branch.

README.md
docs/adoption.md
examples/manifest.json

View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Merge commit title

Merge pull request 'Define the development provisioning-to-controller inbox profile' (#1) from codex/provisioning-inbox-profile into main

Merge commit body

Reviewed-on: https://git.pseudo.design/kaiba/kaiba-contracts/pulls/1

Merge pull request 'Define the development provisioning-to-controller inbox profile' (#1) from codex/provisioning-inbox-profile into main

Reviewed-on: https://git.pseudo.design/kaiba/kaiba-contracts/pulls/1