activity-core/workplans/ACTIVITY-WP-0040-frontend-patterns-feedback.md

---
id: ACTIVITY-WP-0040
type: workplan
title: "Deterministic frontend-patterns feedback collection and reports"
domain: infotech
repo: activity-core
status: blocked
owner: codex
topic_slug: activity-core
created: "2026-09-27"
updated: "2026-09-27"
state_hub_workstream_id: "963bf8b3-536c-5625-b786-60a7b6e7c809"
---

User requested activity-core setup for FEP-WP-0008's unattended loop. This workplan
owns the reporting runtime; it does not claim an admitted repository executor.

## Implement bounded receipt collection

```task
id: ACTIVITY-WP-0040-T01
status: done
priority: high
state_hub_task_id: "b7f391aa-2de4-5f9e-9af7-346bec7e0beb"
```

The frontend-patterns resolver reads fixed-host, commit-pinned source indexes;
validates and reduces immutable receipts; quarantines conflicting histories;
separates synthetic use; reports errors and unknown coverage; emits no tasks or
model calls. New contract tests and existing instruction/sync tests verify this.
Domain definitions project into k8s/railiance/20-runtime.yaml, initially disabled.
Dockerfile.frontend-patterns overlays only two Python files on the deployed worker.

## Deploy, verify sinks and enable schedules

```task
id: ACTIVITY-WP-0040-T02
status: wait
priority: high
state_hub_task_id: "0d0d1d05-9b2d-5eac-b54a-c557b1690afc"
```

Target ADMINISTER @ realm:kubernetes/railiance01. User authorizes setup, but the
estate's 2026-09-21 Kubernetes change gate requires Git/ArgoCD for unmapped targets.
No activity-core ArgoCD application or lower-tier mapping was found. Route through
ArgoCD adoption or an explicit scoped exception before live mutation. Prepare
server dry-run and client diff for only the worker and external-definition
ConfigMap. Observed node requests: 3430m/4000m CPU and 9376Mi memory; verify again
before rollout. Do not rewrite API/router images or unrelated definitions.

After rollout, sync disabled definitions; manually exercise the report sinks;
enable all three domain definitions and matching projections; sync schedules;
record exact receipts and first natural scheduled execution. Rollback restores
activity-core:fi-publication-20260914 and disables the definitions with resync.

## Preserve execution dependency and complete operational handoff

```task
id: ACTIVITY-WP-0040-T03
status: done
priority: high
state_hub_task_id: "8ce5cae1-ebb8-5063-a130-91a1d1fe0679"
```

GLAS-WP-0012 / HFACT-WP-0001 retain production profile readiness and spend custody.
FEP-WP-0008-T03 retains weekly investigation and publication; no legacy fallback.
The resolver always reports execution_ready=false until a separately reviewed
integration replaces that declaration with measured readiness. Source enrollment,
producer hooks, pagination and real-use acceptance remain FEP-WP-0008-T01/T02.
Keep this workplan active until production reporting is evidenced and unresolved
operational tasks have live owners. Zero enrolled consumers is not success evidence.

## Activation evidence — 2026-09-27

Founder explicitly granted the scoped direct-deployment exception in this session;
State Hub decision `e5dd02cb-b5b2-45c8-a600-748ea2ffd31b`. Authority:
`ADMINISTER @ realm:kubernetes/railiance01`, `activation=APPROVED`. Imported tested
image, repeated headroom/dry-run/diff, rolled worker successfully, verified all
three report sinks, enabled/projected definitions and resynced with zero errors.
All three schedules are active with no drift. One-shot Temporal smoke completed
at 11:28:45 UTC, run `182fef14-0795-5fb7-b807-2bdb3c6a8897`, report
`c5446c0a-125b-4703-b964-006aaef46241`; zero tasks and model calls.

Full evidence is frontend-patterns/docs/evidence/2026-09-27-activity-core-activation.json.
T02 remains in progress solely for natural daily/weekly/monthly cadence evidence
(first due September 28 / September 29 / October 1). T03 handoff is complete:
FEP-WP-0008 retains consumers and improvement execution; ACTIVITY-WP-0041 records
the permanent GitOps/adoption/standing-authority work needed to prevent exceptions.
Do not close this workplan until cadence evidence is observed or explicitly handed
off to another live task. No real-consumer value or autonomous edits are claimed.

## Loose-end review — 2026-09-27

T02 is now wait and the workplan blocked on natural cadence evidence. The
September 27 activation/sink smoke already completed the deployable repo work;
first daily/weekly/monthly executions are due September 28 / September 29 /
October 1. A manual rerun cannot satisfy this acceptance condition. Resume T02
when the three natural executions have matching run/report/sink receipts. Keep
existing schedules enabled and retain FEP-WP-0008 ownership of consumer value
and improvement execution. No new task or artificial success evidence was created.