Docs
What ForgeAI Studio is, the pipeline sequence, and key principles
What this is
A production-grade AI persona pipeline. Personas are designed, red-teamed, evaluated, and promoted through a rigorous, structured sequence before reaching production.
Pipeline sequence
Persona Pack → System Prompt → Red-Team → Patch → Re-test → Eval Pack → Judge Prompt → Production
Key principles
- Every artifact carries a tag block:
name@version | eval-status | temp | max_tokens | red-team state | bias facet | eval-pack state - Bias facet check is mandatory on every persona — no exceptions
- Hard gates (AX-05, AX-06) are non-negotiable production blockers
- Judge consistency is prompt-enforced — the model in use accepts no
temperatureparameter; the non-negotiable guarantee is the hard-gate pass/fail computed in code from real scores, never trusted from the judge's own self-report - Repair loops are mandatory on schema validation failure — not best-effort
- Semantic versioning on all assets; all changes logged in the Failure Registry
Deeper reference
- README.md — this page's source, plus current asset state and directory structure
- docs/tech_stack.md — architecture, no-build-step constraint, the Persona Library backend
- personas/orion/orion@2.2.0.md — the Orion orchestrator persona itself
- pipeline-specs/orion-workflow-pipeline.md — full pipeline spec + CI/CD target
- registry/failure-registry.md — all known issues + fixes