coulomb/commerce-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record demand-driven canon federation residuals
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
tegwick 2026-09-06 08:05:54 +02:00
parent 4a5b3d8fcb
commit 2522f94512
1 changed files with 37 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

37
intakes.md Normal file
View file

@ -0,0 +1,37 @@
# Intake records
## COMMERCE-IN-0001 — Commerce service surface demand review
```yaml
id: COMMERCE-IN-0001
kind: intake
lane: blue
title: "Commerce service surface demand review"
status: open
owner: commerce-canon
repo: commerce-canon
origin: residual
origin_ref: CFED-WP-0001
created: "2026-09-06"
updated: "2026-09-06"
description: >-
When a named consumer establishes a need that published canon artifacts cannot satisfy, decide whether a service surface is justified. Record the workload, expected benefit, ownership, operating cost and alternatives before creating implementation work. No service demand was established by foundation closure. This intake preserves the conditional decision without committing to a service. Source: prj-canon-federation CFED-WP-0001-T10.
```
## COMMERCE-IN-0002 — Federated canon consumer adoption review
```yaml
id: COMMERCE-IN-0002
kind: intake
lane: blue
title: "Federated canon consumer adoption review"
status: open
owner: commerce-canon
repo: commerce-canon
origin: residual
origin_ref: CFED-WP-0001
created: "2026-09-06"
updated: "2026-09-06"
description: >-
Track demand for adoption by fin-hub, target-revenue, adaptive-pricing and qonto-assistant. For each consumer with a concrete signal, identify needed concepts and pinned canon revisions, obtain owner-authored acceptance criteria, and route implementation to that consumer repository. Coordinate shared semantic questions with info-tech-canon. None of the four is claimed adopted by foundation closure. No consumer edits or external messages are authorized by this intake. This differs from INFO-WP-0019-T06, which requires independent cadence-contract evidence. Source: prj-canon-federation CFED-WP-0001-T10.
```