CinvanaAI
← All projects

Library · Workflows & capabilities / Code & architecture

Agent Foundry Blueprint Compiler

Turn a capability record into a portable fenced blueprint, then parse it back.

Repository: CinvanaAI/agent-foundry-blueprint-compiler

Recorded synthetic example. Source with a complete offline example.

See the idea in action.

Seven fenced blocks round-trip to one normalized record; a mixed-package fence is rejected.

Example input
A JSON package record containing a Python text-normalizer function.
Captured result
{
  "name": "Normalize Text",
  "round_trip": true,
  "mixed_package_rejected": "All blocks must belong to the same package",
  "formatting_changes_raw_hash_only": true,
  "blueprint_sha256": "7472dc118e36438347ec461cdbf82abd4ab6b894de7f4eb8b6eaad3f54107d38",
  "record_sha256": "14bcb51aa169f11c3bc3669061f16ff33edcf5ffc653510bf9eadfaff09f4f5a",
  "logic_executed": false
}

Try the example.

From the repository root, follow the dependency requirements in the README. This example uses supplied synthetic material.

python -m pip install -e .
python -m examples.demo

Seven fenced blocks round-trip to one normalized record; a mixed-package fence is rejected.

Complete setup and instructions ↗

The interesting part.

Human-readable boundaries and machine-checkable round trips make a capability definition inspectable before execution.

Focused extraction

Where it came from.

Agent Foundry importer, parser and runtime composer inside the historical Python workbench.

Isolates the record/blueprint/runtime boundary and tightens its round-trip grammar.

It is a focused boundary from the integrated application, not its editing UI.

Source ↗

Follow the family: Builder, Factory and the Python Foundry

  • Extracted fromPython Agent Foundry Workbench

    See the integrated setting from which this independently useful mechanism was separated. The standalone boundary has documented public adaptations; this is not a promise of current drop-in interchangeability.

    Source ↗