Description
Ship a fictional pharma regulatory-authoring blueprint (AWS, EKS with k8s-monitoring, Bedrock team profiles, five-agent pipeline) and bring synthkit’s Agent Observability lanes to the current SDK and backend contract. Design, decisions and producer table: doc-0004 (read first; do not re-open its decisions).
Acceptance Criteria
- #1 The pharma-regulatory-authoring blueprint loads under BLUEPRINT_NAMES=* and a live customer-stack push shows conversations, guard steps, online scores, ratings and experiment runs produced by the real backend
- #2 synthkit emits no backend-derived or backend-only family (doc-0004 producer table), proven by read-back
- #3 No forbidden-word hit anywhere, including decompressed corpus files
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Plan
Deliver current wire contract and independently gated provisioning and pipeline components, then real hooks, experiments, shipped blueprint and bounded live read-back. Completed foundations do not close the parent estate acceptance.
Implementation Notes
Owner requested immediate loop closeout; work is parked and no continuation is authorised by background CI events. Preserve delivered source and partial work; resume only under an explicit new instruction, reconciling current Git, board, runtime and the recorded acceptance blockers. Engine hosted AMD64 race/e2e result remains pending at closeout; no full-estate completion or runtime/live activation claim.