This folder contains the public doctrine, report logic, risk categories, templates, and operating principles behind Stackfax.

Stackfax is the report card for Ai stacks.

The goal of these docs is to explain how Stackfax evaluates whether an Ai stack fits the user’s actual workflow, budget, risk level, hardware needs, permissions, and scaling path.

A bigger stack is not always a better stack.

The right stack is the one that fits the job.

• what the user is trying to do
• which tools and models are involved
• what costs money
• what can touch private or business systems
• what requires human approval
• what evidence proves the workflow worked
• what should be rechecked later

Read these first:

• what-is-stackfax.md

• ai-stack-field-guide.md

• beginner-to-builder-stack-path.md

• scoring-rubric.md

• rating-system.md

• badge-definitions.md

• report-ladder.md

These docs define Stackfax report lanes:

• hardware-verdict.md

• hardware-verdicts.md

• mac-mini-decision-tree.md

• openclaw-stack-check.md

• token-burn-audit.md

• model-subscription-fit.md

• business-ai-audit.md

• business-automation-safety-audit.md

• vendor-stack-verdict.md

• stack-migration-fit.md

• executive-audit.md

• pro-report-outline.md

These docs define how Stackfax thinks about trust, control, evidence, and review:

• run-receipts.md

• context-receipts.md

• decision-receipts.md

• evidence-assembly.md

• evaluation-layer.md

• prompt-governance.md

• memory-context-governance.md

• state-before-history.md

• permission-vs-authority.md

• production-readiness.md

• recheck-system.md

• what did the agent see?
• what did it do?
• why did it decide that?
• what evidence supports the result?
• what requires approval?
• what changed?
• what should be rechecked?

These docs define Stackfax cost-control and routing logic:

• token-burn-risk.md

• token-burn-audit.md

• model-routing-doctrine.md

• cost-visibility.md

• model-subscription-fit.md

• token burn
• premium model overuse
• API cost
• subscription overlap
• model routing
• fallback escalation
• context bloat
• cost per useful outcome

These docs define hardware, local model, and local-agent review logic:

• hardware-verdict.md

• hardware-verdicts.md

• mac-mini-decision-tree.md

• local-agent-stack-anatomy.md

• openclaw-stack-check.md

• Mac mini decisions
• local Ai boxes
• GPU rigs
• local vs cloud fit
• Ollama/local model workflows
• dedicated Ai lab setups
• hardware overkill risk

These docs define the business automation lane:

• business-ai-audit.md

• business-automation-safety-audit.md

• workflow-before-agent.md

• process-before-automation.md

• production-readiness.md

• executive-audit.md

• agent-roi.md

• business workflows
• customer data risk
• approval gates
• credential isolation
• process fit
• human review
• automation readiness
• ROI proof
• production readiness

These docs define how Stackfax evaluates agents as operating systems, not just chatbots:

• agent-roi.md

• run-receipts.md

• workflow-before-agent.md

• process-before-automation.md

• permission-vs-authority.md

• production-readiness.md

• recheck-system.md

• agent tasks
• tool use
• authority boundaries
• failure handling
• useful work
• review burden
• run receipts
• rollback and recovery

These docs define context discipline:

• memory-context-governance.md

• state-before-history.md

• context-receipts.md

• prompt-governance.md

• evaluation-layer.md

• memory scope
• RAG
• embeddings
• prompt templates
• prompt drift
• context bloat
• state packets
• source/context receipts

These docs define public research and community behavior:

• rabble-scout-operating-doctrine.md

• gold-reports-workflow.md

• aistackclinic-operating-doctrine.md

• community-standards-plan.md

• field-research-log.md

• what becomes a Gold Report
• what gets project-sourced
• when to reply publicly
• when to ignore
• how to avoid spam
• how public chaos becomes Stackfax doctrine

These docs define what belongs in public versus private systems:

• public-private-roadmap.md

• license-strategy.md

• community-standards-plan.md

• rabble-scout-operating-doctrine.md

Trust is public.

Customer data is private.

The standard can be visible.

The engine does not have to be fully exposed.

Related form docs may live in:

forms/

Important intake files include:

• report-intake-google-form-layout.md

• google-form-build-checklist.md

• free-mini-report-intake-form.md

• quick-report-intake-form.md

Report templates may live in:

templates/

Sample reports may live in:

reports/

• free-mini-report-template.md

• quick-report-template.md

• hardware-verdict-template.md

• token-burn-audit-template.md

• model-subscription-fit-template.md

• business-automation-safety-audit-template.md

• executive-audit-template.md

• sample-beginner-openclaw-starter-stack.md

• sample-business-automation-stack.md

• sample-token-burn-audit.md

• sample-local-hardware-stack-report.md

• sample-model-subscription-fit-report.md

• sample-beginner-to-builder-stack-path.md

• stackfax-self-test-report.md

-Token Burn Risk

-Context Bloat Risk

-Subscription Overlap Risk

-Hardware Overbuild Risk

-Approval Gates Missing

-Credential Isolation Risk

-Customer Data Risk

-Communication Channel Risk

-Fragile UI Automation Risk

-Run Receipts Missing

-Evaluation Layer Missing

-Agent ROI Unclear

-Version Drift Risk

-Migration Risk

-Production Not Ready

-StackChecked

-Token-Smart

-Cloud-First

-Local-Ready

-Hardware Justified

-Human Approval Required

-Customer Data Risk

-Business Automation Ready

-Production Not Ready

-Run Receipts Needed

Use the docs this way:

1. Start with the user’s actual workflow.
2. Pick the closest report type.
3. Check cost, risk, permissions, hardware, and approval gates.
4. Apply relevant badges and risk flags.
5. Explain the verdict with decision receipts.
6. Recommend one next move.
7. Set a recheck trigger.

Stackfax should not reward complexity by default.

Stackfax should reward fit, clarity, safety, cost discipline, evidence, and upgrade path.

After this docs index, the next priority is:

1. Cross-link major docs with Related Docs sections
2. Turn doctrine into report templates
3. Refresh sample reports
4. Build the public intake path
5. Connect Stackfax.com to the free mini report flow
6. Prepare the first paid Quick Report path

The docs are not the product by themselves.

The docs become valuable when they turn into reports, intake questions, user verdicts, and safer Ai stack decisions.

Doctrine becomes useful when it helps someone decide what to build, buy, automate, pause, or recheck.