ewoooc/docs/guides/ai_automation_mainline_work_items.md

AI Automation Mainline Work Items

Updated: 2026-07-17 01:25 Asia/Taipei Governance: global_product_governance_v2 + ADR-038 Current P0: GROWTH-P0-001 comparison coverage truth + autonomous refresh

Source Of Truth

• Production runtime receipt/post-verifier/durable DB receipt is authoritative.
• Gitea main, deploy marker, CD run and production readback are the only source/deploy truth; GitHub remains frozen.
• Source/test/UI/CD green does not mean runtime closure.
• Completion must report program, asset coverage and runtime closure separately.
• PixelRAG visual evidence cannot write formal prices or ai_insights before identity, PromotionGate and internal RAG canary proof.

Ordered P0

Order	ID	Status	Work item	Exit evidence / next machine action
1	SEC-P0-001	Completed	Deny-by-default route access control	governance/evidence/SEC-P0-001-20260711T122758Z.json plus the current runtime receipt prove anonymous matrix 8/8 denied, public /metrics 404, exact internal target up, EwoooC product markers present, Prometheus identity preserved and momo-db unchanged.
2	GROWTH-P0-001	In progress (runtime_partial)	Comparison coverage truth + autonomous refresh	V10.810 is live and retains the growth runtime introduced at exact Gitea object 2647632660673e9f1533e61922c96e4fb4adcb40. Controlled run 34999f5314054f09909663b46fc42ee2 scanned 20, verified/wrote/read back one exact offer and raised the fixed cohort to 25 ready + 1 candidate validation + 24 unmatched, 50% count and NT$211,667 / NT$354,062 = 59.782% revenue. Follow-up run e1508ec3a49241d1965bc99d428b0325 found 19 candidates but safely wrote zero because none passed strict identity/variant/unit verification; its independent terminal is degraded_no_safe_candidate. Yahoo remains durably active + enabled + write_enabled, and the durable readback proves formal_source_activated=true even when the latest run is verified no-write. Formal runtime remains 2/15. Next: retry the unresolved revenue-weighted batch only with fresh source evidence, then add the next approved structured marketplace adapter without relaxing promotion gates.
3	SEC-P0-002	In progress (canary_ready)	Database identity + least-privilege RBAC	V10.789 is live and governance/auth_identity_runtime_receipt.json verifies required tables, two active admins, durable lockout, session revocation, trusted proxy policy and no-secret mutation audit readiness. Runtime is intentionally hybrid because zero database-admin success receipts have been captured; auto retires shared authority after two durable successes without a manual review gate. Next: capture database-admin login receipts and verify automatic database-only cutover.
4	SEC-P0-003	In progress	Webhook trust and replay protection	Telegram secret-token verification code exists; production secret activation remains unproven. Exit: secret provisioned outside source, required mode enabled, invalid-secret 401 and authorized callback canary pass.
5	SUPPLY-P0-001	In progress	Gitea-only secure software supply chain	Gitea-native checkout, secret-safe .dockerignore, commit-bound source receipt and governance gate are active. Exit: exact dependency lock, internal SAST/SCA/secret scan, SBOM, image digest/provenance, vulnerability SLA and production digest readback.
6	GOV-P0-001	In progress	Canonical full asset graph + runtime reconciliation	governance/ewoooc_asset_inventory.json seeds hosts, services, data, AI, routes, supply chain, observability and recovery. Exit: same-run probe receipt for every asset; drift auto-creates work items.
7	GOV-P0-002	Not started	Unified controlled-apply envelope	Introduce one trace_id/run_id/work_item_id across sensor, identity, SOT diff, decision, risk, dry-run, execution, verifier, rollback/retry and learning acknowledgement. Start with EventRouter + AutoHeal.
8	RAG-P0-001	In progress (scheduled_source_ready_runtime_unproven)	Internal RAG candidate canary	V10.811 source adds internal_rag_candidate_canary_service, read-only authenticated API, CLI, smoke adapter and a default-enabled daily 04:45 scheduler run. The bounded executor processes at most one candidate, requires both GCP-A/GCP-B, runs pgvector similarity inside SET TRANSACTION READ ONLY, always rolls back, writes only a canary artifact/scheduler receipt and records Telegram acknowledgement; it cannot write ai_insights or price tables. Exit still requires production candidate/executed receipts, immutable model reference, controlled RAG_ENABLED shadow activation, query/hit telemetry and feedback readback. Source/test readiness is not runtime closure.
9	MCP-P0-001	In progress (federation_source_ready)	MCP/RAG production runtime closure	V10.796 source adds a strict public aggregate receipt for canonical ewoooc and momo-pro-system identities without opening authenticated internal APIs or exposing endpoint/tool payload data. Exit still requires V10.796 production /health, two fresh AWOOOI durable receipts with fingerprint recompute, live MCP servers/router/RAG, approved caller/tool boundary and production query canary. Current source readiness must not be reported as runtime closure.
10	SEC-P0-004	Not started	Security operations lifecycle and metrics	Add durable security incident state and publish MTTA, MTTR, recurrence, false positive, human intervention, verifier pass, rollback and freshness. Exit: detect-to-learn production receipt.
11	REL-P0-001	In progress (runtime_verified_cd_degraded)	Formal deploy and visible proof discipline	Production V10.810 runs exact Gitea object 911393190ded015e384e438c26b68faf50ec260c; dev merge e56c613399affb5cf0134eea44b7f78aa8134943 carries the same source. Host 110 still exposes only paused vibework-dedicated-runner, with no matching EwoooC runner, so this release has no formal CD execution receipt. The controlled fallback archive SHA-256 is cd0607d593fd16c8281b5f01839d20d7eba493f49d363cb197c30966c25be5ee; archive, checksum manifest and rollback (02e73678125ee0c8908a42be8fff479287180fa2c06f6efe7dce70c2ce7339a4) are retained at /home/ollama/momo-deploy-backups/analytics-ui-20260716T080302Z-9113931. Internal/external /health is healthy at V10.810; only momo-app was recreated, while scheduler ID 9af8e31fd0eb90f74ce5894af1ae1fbc511362ec90df142fde6442cf737d1181, Telegram bot ID 1d4bd922f6ad1252177ba40f16ea172dcd5eb1de1b4c999c00f4a3141bd06ca5 and momo-db immutable ID cd092451cb5fd555d0ffff70642e109f3b742882c418beeab631793d1e9dc55d did not change. Runner recovery remains a release-governance gap and is not replaced by fallback evidence.

GROWTH-P0-001 Fixed Execution Lanes

These lanes are one ordered current P0, not optional side work. They must advance in this order and keep formal-price writes behind verified same-item evidence.

Lane	Status	Production baseline	Next machine action
A. Sales freshness	In progress (sla_runtime_closed_source_redundancy_partial)	Latest sales date 2026-07-13; before the 2026-07-15 20:00 cutoff, raw lag is 2 but SLA lag is 0, state is grace and decisions remain released. Scheduler receipt 0f24219e0bbb4740b7ad6645e7952296 and explicit canary receipt 6e2df008f65544fe8e557c11ff0dbb93 both persisted completed_no_write; durable decision is no_candidate_fresh_no_write. Live and persisted readiness now agree at Google Drive 1/4; HTTPS, IMAP and local remain disabled.	Continue automatic report-arrival reconciliation. At/after 20:00 require 2026-07-14 or automatically block decision use, emit the bounded upstream action and verify the next arrival receipt; keep source redundancy partial until another approved source is live.
B. Verified same-item evidence	In progress	TOP50 fixed cohort: 25 verified, 1 candidate/source validation, 24 unmatched. Count coverage is 50%; revenue-weighted coverage is NT$211,667 / NT$354,062 = 59.782%. V10.810 preserves fingerprint 7b74504fcc1e1801c2ca2b42; run 34999f5314054f09909663b46fc42ee2 added one independently verified offer (+2.0pp count, +1.89pp revenue), while run e1508ec3a49241d1965bc99d428b0325 correctly ended no-write. Their durable artifact SHA-256 values are 994beba6dfa70ef8c50031f130916ee155657dd77ac8a2f59b6530b491d45d1e and e58be7bb07599871a8f318ad63885bd868c786b0144b81ba0980ae80cf556541.	Retry unresolved candidates only after fresh evidence arrives, preserve deterministic identity/unit/variant gates, and publish count/revenue deltas against the same fingerprint per run.
C. Platform runtime coverage	In progress (runtime_canary_activated)	V10.810 is live. Yahoo is durably active and exact-offer canary readback remains valid; an already-active canary now returns already_active_verified, state_changed=false and writes_database_count=0, while latest no-write receipts no longer erase durable activation truth. Formal runtime is 2/15; PixelRAG remains evidence-only.	Continue bounded refresh on schedule, monitor expiry/recurrence/rollback signals, then implement the next approved structured source contract for Shopee, Coupang, ETMall, Friday or Rakuten without treating blocked pages as product data.

AI Agent Product Integration Acceptance

This is an acceptance surface inside the current growth P0; it does not reorder the P0 queue. V10.811 source replaces class/method-presence optimism with a seven-day production telemetry readback.

Layer	Current status	Exit evidence
Source and scheduler wiring	Source ready (4/4)	Hermes, NemoTron, OpenClaw and ElephantAlpha source markers plus scheduler ownership are machine-read and reported separately from runtime.
Agent runtime activity	Production baseline partial (2/4)	The pre-release live readback found Hermes 1 call / 1 error, OpenClaw 13 calls / 4 errors, and zero NemoTron/ElephantAlpha calls in seven days. Exit requires all four active and healthy in the bounded window, without treating a configured fallback as activity.
MCP/RAG dependency	Runtime disabled / telemetry empty	Production currently reports MCP_ROUTER_ENABLED=false, RAG_ENABLED=false, zero mcp_calls and zero rag_query_log activity. Exit requires enabled approved routes, live health, non-zero agent/product telemetry and the internal RAG candidate canary.
Controlled automation closure	Runtime partial	/api/ai-automation/agent-product-integration, CLI and smoke must report Detect -> Normalize -> Correlate -> Decide -> Check -> Controlled Apply -> Verify -> Retry/Rollback -> Learn/Writeback. Completion requires bounded execution, linked outcome/incident verification and durable learning evidence; aggregate source presence is insufficient.

Analytics Period-Linkage Closure

This bounded interruption is closed and control returns to GROWTH-P0-001 without changing its lane order.

Completion layer	Status	Production evidence
Program	Completed for the four primary analysis tabs	Daily sales, sales analysis, growth analysis and monthly summary now share one canonical day/month/range contract; cross-tab links preserve the selected period.
Asset coverage	4/4 pages and 2/2 sales async APIs verified	Daily KPI/calendar/charts/Top 10, growth KPI/series, monthly KPI/tables/charts and sales KPI/charts/YoY/detail table all use the active period. Historical current-snapshot mixing and blank monthly charts are replaced by explicit honest states.
Runtime closure	Completed in V10.810 at 911393190ded015e384e438c26b68faf50ec260c	2026-04 daily stays inside April and bounds extreme DoD/WoW values with traceable markers; growth single-point series remain visible; sales consumes the real chart_values payload and aggregates repeated SKU rows before ranking; monthly requests are abortable/deduplicated and publish explicit loading/error/ready states. External HTTPS serves the exact tested JS/CSS checksums and internal/external /health report V10.810.
Verification	Passed; formal CD still degraded	Final regression: 2,123 passed / 9 skipped / 0 failed; focused analytics contracts: 49 passed. The automated visual guard passed 12/12 combinations (4 pages x desktop/tablet/mobile), covering 126 chart-target observations, period links, actual pixels/elements, honest empty states, date-tick density, console errors and overflow. Formal CD remains degraded because no matching runner executed the release.

P1

Order	ID	Status	Work item	Exit evidence / next machine action
12	RES-P1-001	Not started	Backup/offsite/restore automation	Fresh checksum and offsite coverage plus isolated non-destructive restore drill with measured RPO/RTO.
13	PLAT-P1-001	Not started	Non-root container and capability hardening	Shadow non-root image, writable-path inventory, capability drop/read-only filesystem canary, three-app rollout.
14	APPSEC-P1-001	In progress	CSP and DOM/XSS hardening	Security headers are present and CSP is report-only. Collect violations, remove high-risk innerHTML/inline sinks, then enforce CSP by canary.
15	APPSEC-P1-002	Not started	Unsafe shared-cache serialization removal	Replace writable pickle caches in dashboard/daily-sales/EDM/sales with constrained JSON or signed schema.
16	ARCH-P1-001	In progress	Split oversized policy/executor/verifier modules	Current top debts include 44k-line PChome mapping and 14k-line smoke service. Split by bounded family and independent tests.
17	UX-P1-001	In progress	Professional full-site UI/UX	V10.810 closes chart rendering defects across all four primary analysis tabs: real payload values render, single points stay visible, extreme percentages no longer flatten normal data, dense date labels auto-skip, Top 50 vendor content uses bounded zoom, and loading/error/empty states are explicit. The 12/12 desktop/tablet/mobile visual matrix has zero horizontal overflow. The broader site-wide first-viewport, progressive-disclosure, accessibility and loading/error/degraded-state audit remains in progress.
18	PIXELRAG-P1-001	Not started	Ollama-first multimodal embedding benchmark	Verify approved visual embedding on GCP-A -> GCP-B -> 111 and design pgvector-compatible visual metadata; FAISS remains disallowed without ADR.
19	MARKET-P1-001	In progress	Marketplace source contracts	Yahoo Shopping remains active in V10.810 production with public-boundary allowlists, bounded streaming/rate, provenance, current product-detail readback, stock/spec/variant guards, source-specific promotion partition, idempotent exact canary activation and durable activation readback across no-write runs. Four fresh verified Yahoo offers now contribute formal evidence across completed batches; non-exact and unit-price candidates do not. Shopee, Coupang, ETMall, Friday and Rakuten still require equivalent structured contracts, and blocked pages remain non-product data.
20	QA-P1-001	In progress	Deterministic test and CI governance	V10.810 final broad regression is 2,123 passed / 9 skipped / 0 failed; analytics contracts are 49 passed, and the new runtime chart guard passes 12/12 page/viewport cases with actual pixel/element and console assertions. Production host parity is 18/18 files and public HTTPS parity is 9/9 key JS/CSS assets. No matching EwoooC runner executed this release, so CI/CD parity is not claimed and exact-object fallback receipts remain separate evidence.

P2

Order	ID	Status	Work item	Exit evidence / next machine action
21	GOV-P2-001	Not started	Continuous NIST/ASVS control trend	Persist governance snapshots, compare control/asset/runtime drift and create ordered work items automatically.
22	DATA-P2-001	Not started	Data classification and retention enforcement	Classify business, personal, operational and model data; automate retention, deletion eligibility and audit evidence without destructive default actions.
23	CHAOS-P2-001	Not started	Controlled resilience exercises	Run non-destructive model-host, MCP, queue, Telegram and app-container failure drills with rollback and learning receipts.

Completed Foundations

These are reusable foundations, not proof that the full program is complete.

Status	Capability	Current boundary
Completed	Multi-commerce PixelRAG visual evidence for momo, pchome, shopee_tw, coupang_tw, yahoo_shopping_tw, etmall_tw, friday_tw, rakuten_tw	Evidence-only; blocked pages are not product data.
Completed	External MCP/RAG capability inventory	Registry/integration readback exists; runtime enablement remains P0.
Completed	PixelRAG receipt -> RAG candidate replay	Candidate-only; no formal knowledge or price write.
Completed	Source-contract replay worker	Public-boundary artifact receipts only.
Completed	Marketplace adapter preflight and dry-run	Deterministic no-write contracts.
Completed	Marketplace identity matcher replay	Candidate identity only.
Completed	PromotionGate replay	No production write.
Completed	Embedding-signature guard replay	Signature readiness only.
Completed	Candidate knowledge replay	Internal RAG preview only; no DB/model call.
Scheduled source ready	Internal RAG candidate canary	Daily bounded pgvector/Ollama canary exists in V10.811 source with same-run identity, rollback/no-write terminal and Telegram acknowledgement; production execution, model pin and RAG shadow activation remain P0.
Completed	PixelRAG application portfolio	Commerce/RAG/UX/ops/marketing/governance inventory.
Completed	Ollama-first VLM route readiness and replay worker	Evidence-bound artifact output; no direct price write.
Completed	Platform probe worker	Shopee/Coupang barriers become structured fallback/backoff receipts.

Definition Of Done

A work item can be Completed only when the same production run contains:

1. sensor/source receipt;
2. normalized canonical asset identity;
3. source-of-truth diff;
4. AI decision and candidate action;
5. risk/policy decision;
6. check-mode/dry-run receipt;
7. idempotent bounded execution receipt;
8. independent post-verifier and rollback/no-write terminal;
9. incident/Telegram/KM/RAG/MCP/PlayBook durable acknowledgement.

Missing any stage means partial, degraded or blocked_with_safe_next_action.