zfc

Zero Framework Cognition Principles

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Zero Framework Cognition (ZFC) skill provides a rigorous architectural framework for building high-reliability AI agents. It solves the problem of unpredictable agent behavior by strictly separating 'reasoning' (delegated to AI) from 'execution' (handled by a deterministic code shell). By enforcing pure orchestration and structural safety, it ensures that AI agents remain observable, safe, and easy to debug in production environments.

Use Cases

  • Architecting Deterministic AI Agents: Designing systems where the application acts as a safe 'plumbing' layer, handling file IO and state management while delegating all complex logic to the AI.
  • Implementing Safety Guardrails: Establishing 'don’t run without approval' gates and budget caps to prevent autonomous agents from performing unauthorized or expensive actions.
  • Standardizing AI-to-System Interfaces: Using mechanical transforms and schema validation to ensure that AI-generated decisions are correctly formatted and safe to execute within a local environment.
  • Improving Agent Observability: Utilizing mission journaling and lifecycle tracking to maintain a clear audit trail of AI decisions and mechanical executions.
namezfc
descriptionZero Framework Cognition Principles

ZFC (Zero Framework Cognition) Principles

Core Architecture Principle: This application is pure orchestration that delegates ALL reasoning to external AI. We build a “thin, safe, deterministic shell” around AI reasoning with strong guardrails and observability.

✅ ZFC-Compliant (Allowed)

Pure Orchestration

IO and Plumbing • Read/write files, list directories, parse JSON, serialize/deserialize • Persist to stores, watch events, index documents

Structural Safety Checks • Schema validation, required fields verification • Path traversal prevention, timeout enforcement, cancellation handling

Policy Enforcement • Budget caps, rate limits, confidence thresholds • “Don’t run without approval” gates

Mechanical Transforms • Parameter substitution (e.g., ${param} replacement) • Compilation • Formatting and rendering AI-provided data

State Management • Lifecycle tracking, progress monitoring • Mission journaling, escalation policy execution

Typed Error Handling • Use SDK-provided error classes (instanceof checks) • Avoid message parsing

❌ ZFC-Violations (Forbidden)

Local Intelligence/Reasoning

Ranking/Scoring/Selection • Any algorithm that chooses among alternatives based on heuristics or weights

Plan/Composition/Scheduling • Decisions about dependencies, ordering, parallelization, retry policies

Semantic Analysis • Inferring complexity, scope, file dependencies • Determining “what should be done next”

Heuristic Classification • Keyword-based routing • Fallback decision trees • Domain-specific rules

Quality Judgment • Opinionated validation beyond structural safety • Recommendations like “test-first recommended”

🔄 ZFC-Compliant Pattern

The Correct Flow

  1. Gather Raw Context (IO only) • User intent, project files, constraints, mission state

  2. Call AI for Decisions • Classification, selection, composition • Ordering, validation, next steps

  3. Validate Structure • Schema conformance • Safety checks • Policy enforcement

  4. Execute Mechanically • Run AI’s decisions without modification