Deterministic Runtime
Documentation.

Architectural reference for Halfbot's production engines, data contracts, human-in-the-loop verification gates, and security perimeter.

Every Halfbot engine separates stochastic AI generation from deterministic structural execution. Foundation models propose drafts; mathematical constraints and human operators authorize production output.

DOCUMENTATION INDEX

01 // Packaging Factory Specv2.4
02 // StudioCut Engine SpecSTAGING
03 // TAH Transaction Protocolv1.5
04 // Zero-Trust Security RulesLOCKED

CORE SPECIFICATIONS // ENGINE & PROTOCOL REFERENCEBUILT ON VISIBLE LOGIC

01 // DETERMINISTIC ARTWORK & REGULATORY ENGINE

Packaging Factory Pipeline

01Normalized SKU & multi-locale corpus ingestion with canonical SHA-256 base hashing (§F9).
02Group-qualified structural slot locking (`heading`, `dosage`, `ingredients`, `warnings`).
03Donor-locale regulatory validation (units like `mg` vs `mcg` are never silently altered).
04Bounded ±15% typographic calibration corridor for multi-language text expansion.
05Print-ready CMYK / PDF-X4 vector dieline generation after explicit operator approval (§C4).

02 // CONTINUITY-LOCKED VIDEO PRE-PRODUCTION

StudioCut Media Pipeline

01Script and brief ingestion into deterministic scene, shot, and dialogue graphs.
02Persistent character identity, wardrobe, and lighting reference anchoring across shots.
03Frame-accurate storyboard and animatic sequencing with voiceover timing locks.
04Multi-aspect commercial cutdown generation (16:9 Master, 9:16 Vertical, 1:1 Social).
05Export to standard NLE timelines and render queues with full asset lineage.

03 // TRANSACTIONAL AGENT HUB & SANDBOX EXECUTION

TAH Control Plane Protocol

01Every task opens an isolated transaction (`initTransactionBranch`) on `feature/<taskId>`.
02Research and synthesis artifacts are confined to `drafts/<taskId>/` (Context Firewall).
03Automated contract and security test suites execute before any merge candidate is accepted.
04Atomic `verifyAndCommit` merges verified work or triggers instant branch rollback on failure.
05Immutable session telemetry persisted to disk logs with bounded in-memory state.

04 // ZERO-MODEL-EXPOSURE & COST-DOS RAILS

Security & Spend Governance

01Zero Model Exposure: client requests cannot specify or override provider model names.
02Server-side prompt sanitization strips control characters, role delimiters, and markup injection.
03Per-service Firestore spend counters enforce strict daily and per-job budget caps.
04All foundation model calls route exclusively through the internal LiteLLM security proxy.
05Role-based access separation between Customer Portal (`/dashboard`) and Command Center (`/admin`).

CONTRACT-FIRST API BOUNDARY

Strict Separation of Drafts & Production State.

All internal and partner API endpoints enforce strict schema validation before invoking any compute or model pipeline. Below is an excerpt from the Packaging Factory localization & render contract:

// POST /api/packaging/render-batch (Contract Excerpt)

{
  "template_id": "xor-a-pharma-30cap-v2",
  "job_id": "sha256_8f91c4a0d2e7...",
  "items": [
    {
      "sku": "XOR-A-30",
      "locale": "DE",
      "calibration_corridor": "±15%",
      "operator_approved": true
    }
  ]
  // Note: Any "model" field in client payload is rejected (Zero Model Exposure)
}

PRE-LAUNCH SANDBOX & SDK ACCESS

Explore the Live Platform or Request API Credentials.

During our pre-launch phase, external API keys and webhook integrations are provisioned directly for design partners and technical due diligence teams.

LAUNCH READINESS & SEED ROUND

System Status & Roadmap (/status)

MONOREPO & SECURITY AUDIT

Repository Architecture (/repository)

Request Pilot API Key Investor Deck