Library · Workflows & capabilities

Agent Assembly Runtime

Edit one agent definition and rebuild its group, task and memory views.

Repository: CinvanaAI/agent-assembly-runtime

Explore the repository ↗Try or inspect it ↓

Recorded synthetic example. Source with a complete offline example.

See the idea in action.

Edit the canonical definition, rebuild its projections, reload the changed groups and reject an unknown task field.

Example input

Review Bot with Outcasts and Research groups and one Summarize task.

Captured result

{
  "name": "Review Bot",
  "groups": [
    "Outcasts",
    "Research"
  ],
  "files": [
    "Review_Bot/Outcasts.group.json",
    "Review_Bot/Research.group.json",
    "Review_Bot/Review_Bot.json",
    "Review_Bot/Summarize.task.json"
  ],
  "rejected_typo": "task entry 1 contains unknown field(s): task_staus",
  "embedded_source_executed": false,
  "groups_after_edit_and_restart": [
    "Outcasts",
    "Review"
  ],
  "projected_task": "Summarize",
  "stale_research_projection_removed": true
}

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.walkthrough

Edit the canonical definition, rebuild its projections, reload the changed groups and reject an unknown task field.

Complete setup and instructions ↗

The interesting part.

One canonical document owns task membership; other files are rebuildable projections.

Focused extraction

Where it came from.

Assembly subsystem of the historical Python Agent Foundry workbench.

Removes host handoff coupling and accepts a caller-selected assemblies directory; retains schema, validation, projection and memory machinery.

The independent package manages documents; it is not the complete agent workbench.

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 ↗