Skip to main content

AI Factory Workflow — AI Factory MVP smoke workflow docs-only validation

AI Factory Workflow — AI Factory MVP smoke workflow docs-only validation

Created: 2026-05-26T13:55:18.621Z
Priority: L
Domain: product
MC route: product
Recommended company: AgentForge + Skybound
Factory mode: internal MVP, no production mutation by default

Goal

AI Factory MVP smoke workflow docs-only validation

Routing

  • Selected MC route: product
  • Recommended company: AgentForge + Skybound
  • Routing evidence: captured in the JSON evidence package.

P2P Pair Programming Policy

  • Required: no
  • Reason: not in controlled risky rollout scope
  • Mode: block

If P2P is required, the builder must use bounded Company Mesh peer verification before MC ready/done. The safe default remains prewire + prompt injection + MC gate, not automatic verifier send at dispatch time.

Execution Plan

  1. AI Factory plan/spec refinement (product, M) — Refine scope, acceptance criteria, risks, and non-goals for: AI Factory MVP smoke workflow docs-only validation. No implementation.
  2. AI Factory build/implementation slice (product, M) — Implement the approved first slice for: AI Factory MVP smoke workflow docs-only validation. No production mutation by default.
  3. AI Factory independent verification (qa, M) — Independently verify evidence, commands, and acceptance criteria for: AI Factory MVP smoke workflow docs-only validation. Do not rely on builder summaries.
  4. AI Factory docs and BookStack update (general, M) — Update BookStack/status docs and record evidence/lessons for: AI Factory MVP smoke workflow docs-only validation.
  5. AI Factory postflight and memory writeback (post-build, M) — Postflight: summarize outcome, cost, evidence paths, blockers, and queue memory/LightRAG writeback for: AI Factory MVP smoke workflow docs-only validation.

Guardrails

  • No production deploy or mutation unless a later task explicitly approves it.
  • Evidence paths must exist before ready/done claims.
  • Memory/LightRAG is advisory, not evidence.
  • Final QA remains mandatory for user-facing/deploy-impacting work.

Expected Evidence

  • MC parent task id.
  • Linked subtasks.
  • Process tracker id.
  • BookStack URL.
  • JSON evidence file under /tmp/alai/ai-factory/.
  • P2P mesh thread id where required.

No comments to display

Back to top