coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Prepare approved reporting repair and monthly review inputs

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e738-9e15-7600-87e6-90dec3a7beef
This commit is contained in:
tegwick 2026-09-28 11:22:19 +02:00
parent 9baf6f1829
commit a18d83f74a
16 changed files with 663 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

43
feedback/ConsumerIntegration.md Normal file
View file

@ -0,0 +1,43 @@
# First consumer integration
FEP-WP-0008 T01/T02 owns this bounded handoff; no consumer is enrolled by this file.
Use the common instruction owner for the selected repository. Do not install a fleet
mandate, reopen a finished task, or invent product work to manufacture adoption.
## Eligibility
A real, open frontend task must need a decision about shared edits, offline recovery,
navigation/rendering, interaction or feature boundaries. The consumer keeps its own
implementation authority. A deployment repair or documentation-only inspection of
this pattern repository is not an external frontend use. Unsupported contexts should
produce an explicit no-match decision, not a forced pattern selection.
## Short planning and closeout instruction
> For eligible frontend architecture work, query
> `capability.infotech.frontend-pattern-language` through hosted reuse-surface.
> Read START.md and the full applicable contracts in the pinned reference release.
> Record its version, packaging revision and manifest digest with selected/rejected
> CAND IDs, task constraints, alternatives and unmet conditions in the task's decision
> note. At closeout, emit an immutable PatternUseReceipt event and index it with its
> SHA-256; unknown outcome is valid. At the first linked test/review/incident, append
> an outcome event with the preceding event digest. Never edit the earlier receipt,
> invent helpfulness, or treat model judgment as observed user benefit.
The [receipt template](../templates/PatternUseReceipt.yaml) and
[index/enrollment contract](README.md) define exact fields. Pin the packaging
revision in [releases.json](../reference/releases.json), not the latest research
HEAD. Read [unsupported contexts](../reference/0.1/README.md) before selecting.
## Acceptance
Before adding an actual consumer to `sources.json`, verify its published receipt
index and immutable event hashes at a concrete revision. Check the source through
activity-core's existing validator/collector. Keep a decision-only unknown outcome
unknown until a linked outcome arrives. Fixture positive/negative paths test the
collector; they do not satisfy real-use acceptance. Enrollment is limited to the
existing allowlist and collection bounds in the runbook.
Hosted registration currently needs the routed OpenBao write credential. Public
index publication is verified, but lookup/registration and a real consumer receipt
must be evidenced separately. Do not infer discovery success from this instruction.