AI Factory V2 — Workflow Templates and Status Pages

Standard internal templates for AI Factory workflows.

Local source directory: /Users/makinja/system/specs/ai-factory/templates

README.md

# ALAI AI Factory V2 Templates

Reusable BookStack/MC templates for internal AI Factory workflows.

These templates support the standard flow:

1. CEO/operator request
2. Workflow status page
3. Evidence package
4. Postflight and lessons learned

## Files

- `request-template.md` — intake/request template for a new AI Factory workflow.
- `workflow-status-template.md` — running status page template for MC parent/process/subtasks.
- `evidence-package-template.md` — evidence bundle template for ready/done review.
- `postflight-lessons-template.md` — postflight summary and lessons template.

## Guardrails

- Evidence paths must point to existing files or command output artifacts.
- Memory, HiveMind, and LightRAG are advisory and must not replace evidence.
- P2P peer verification is required only when current policy classifies the task as risky/H/backend/core/security/user-facing/deploy-impacting.
- Final QA/MC gates remain mandatory.
- No deploy or production mutation unless the workflow explicitly authorizes it.

request-template.md

# AI Factory Request — <goal>

**Request date:** <YYYY-MM-DD>  
**Requester:** <name/role>  
**Owner:** <john|agent|company>  
**Priority:** <H|M|L>  
**Domain/route:** <backend|frontend|devops|qa|security|product|data|general>  
**Recommended company:** <CodeCraft|Vizu|FlowForge|Proveo|Securion|AgentForge|Skybound|John>

## 1. Goal

<One or two paragraphs describing the business/user outcome.>

## 2. Scope

### In scope

- <item>

### Out of scope

- <item>

## 3. Acceptance Criteria

- [ ] <observable criterion with evidence path or command>
- [ ] <observable criterion with evidence path or command>

## 4. Risk Classification

- P2P pair programming required: <yes|no|unknown>
- Reason: <policy reason or classification output>
- Production/deploy impact: <yes|no>
- Security/data sensitivity: <yes|no>

## 5. Planned Workflow Objects

- MC parent task: <#id or pending>
- MC process tracker: <process-id or pending>
- BookStack status page: <url or pending>
- Evidence package: <path or pending>

## 6. Evidence Expectations

- Local spec path: `<path>`
- Test/build evidence: `<path>`
- P2P verifier thread/message: `<mesh-thr-* / mesh-msg-* or n/a>`
- Final QA evidence: `<path or n/a>`

## 7. Guardrails

- No production mutation unless explicitly approved.
- No unsupported claims without existing evidence paths.
- Memory/LightRAG/HiveMind may support context but are not final evidence.

workflow-status-template.md

# AI Factory Workflow Status — <goal>

**Status:** <draft|active|blocked|ready_for_review|done>  
**Updated:** <YYYY-MM-DD HH:mm TZ>  
**MC parent:** <#id>  
**Process:** `<process-id>`  
**BookStack request/spec:** <url>  
**Owner:** <name/agent>

## Summary

<Current state in 3-5 bullets.>

## Workflow Map

| Step | MC task | Owner/company | Status | Evidence |
|---|---:|---|---|---|
| Plan/spec | <#id> | <owner> | <status> | `<path/url>` |
| Build/implementation | <#id> | <owner> | <status> | `<path/url>` |
| P2P pre-verifier | <#id/thread> | <agent/company> | <status> | `<mesh/path>` |
| Final QA/verification | <#id> | <owner> | <status> | `<path/url>` |
| Docs/postflight | <#id> | <owner> | <status> | `<path/url>` |

## Current Evidence

- Implementation evidence: `<path>`
- P2P evidence: `<path or n/a>`
- Smoke/test evidence: `<path>`
- BookStack/docs evidence: `<path/url>`

## Risks and Blockers

| Blocker | Owner | Since | Next action |
|---|---|---|---|
| <blocker> | <owner> | <date> | <action> |

## Next Actions

1. <next action>
2. <next action>
3. <next action>

## Decision Log

| Date | Decision | Evidence/why |
|---|---|---|
| <date> | <decision> | `<path/url>` |

## Claim Discipline

- Every completion/status claim above must have an existing evidence path or command output.
- If an evidence path is missing, mark the item `pending` or `blocked` instead of claiming completion.

evidence-package-template.md

# AI Factory Evidence Package — <goal>

**Generated:** <timestamp>  
**MC parent:** <#id>  
**Primary task:** <#id>  
**Owner:** <owner>  
**BookStack:** <url>

## Verdict

**Status:** <PASS|PARTIAL|BLOCKED>  
**Reason:** <short evidence-based reason>

## Evidence Index

| Evidence type | Path/ID | Status | Notes |
|---|---|---|---|
| Local spec | `<path>` | <exists/missing> | <notes> |
| Implementation diff/file list | `<path/command>` | <exists/missing> | <notes> |
| Syntax/build check | `<path/command>` | <pass/fail/not-run> | <notes> |
| Tests/smoke check | `<path/command>` | <pass/fail/not-run> | <notes> |
| P2P verifier | `<mesh-thr-* / mesh-msg-* / path>` | <pass/partial/blocked/n/a> | <notes> |
| Final QA | `<path>` | <pass/partial/blocked/n/a> | <notes> |
| BookStack/docs | `<url/path>` | <exists/missing> | <notes> |

## Commands Run

```bash
# command

Result: <pass/fail>
Output artifact: <path>

P2P Verification

Required by policy: <yes|no>
Thread: <mesh-thr-...>
Prompt message: <mesh-msg-...>
Response message: <mesh-msg-...>
Materialized evidence: <path>
End state: <PASS|PARTIAL|ANSWERED|BLOCKED|DECLINED>

Known Gaps

Final Notes

No deploy/production mutation unless evidence explicitly says otherwise.
Memory/LightRAG/HiveMind writeback is advisory and should be listed separately from review evidence.


## postflight-lessons-template.md

```markdown
# AI Factory Postflight — <goal>

**Date:** <YYYY-MM-DD>  
**MC parent:** <#id>  
**Process:** `<process-id>`  
**Owner:** <owner>  
**Final status:** <done|partial|blocked>

## Outcome

- Delivered: <what changed>
- Not delivered: <remaining gaps>
- User/business impact: <short statement>

## Evidence

- Primary evidence package: `<path>`
- BookStack status/spec: `<url>`
- P2P verifier evidence: `<path or n/a>`
- QA/test evidence: `<path or n/a>`

## Timeline

| Time | Event | Evidence |
|---|---|---|
| <time> | <event> | `<path/url>` |

## What Worked

- <lesson>

## What Failed / Slowed Us Down

- <lesson>

## Metrics

| Metric | Value | Source |
|---|---:|---|
| Total MC tasks | <n> | `<command/path>` |
| P2P attempts | <n> | `<command/path>` |
| P2P pass/partial/blocked | `<n/n/n>` | `<command/path>` |
| Rework count | <n> | `<command/path>` |
| Approx cost | <value/unknown> | `<path>` |

## Follow-up Tasks

- <#id> — <title/status>

## Knowledge Writeback

- Memory writeback: <queued|ok|blocked>
- HiveMind writeback: <queued|ok|blocked>
- LightRAG outbox: <queued|ok|blocked>
- Evidence: `<path>`

## Recommendation

<Continue / pause / expand / revise policy, with evidence-based reason.>

Notes

These templates are internal operating docs, not product/customer promises.
Evidence paths must exist before ready/done claims.
P2P verifier evidence complements but does not replace final QA/MC gates.