Project state survives
Progress, decisions and relevant memory persist independently from any single model session or worker.
Tenrec is a persistent AI software runtime built around short-lived specialized workers and selective project memory. The project keeps its validated state while each worker receives only the context needed for bounded work.
This walkthrough explains how a software goal becomes bounded specialist work, how failures become explicit repair tasks, and how validated outcomes persist as project memory.
Detect important incoming emails, classify them and post relevant alerts to Slack.
Keep the integration reliable and testable.
Progress, decisions and relevant memory persist independently from any single model session or worker.
Specialists are created for bounded work, then disappear. No single long-lived worker becomes the project.
Tenrec does not keep injecting an ever-growing transcript. It selects compact memory relevant to the current task.
Deterministic validators and governance rules decide whether an execution is accepted, retried, escalated or stopped.
Tenrec decomposes AI software work into explicit layers so planning, memory, execution, evaluation and governance can be inspected independently.
A compact classifier maps incoming work to known task archetypes and gives the planner an explicit starting point.
The planner selects worker roles, tools, required context, validators and a concrete execution sequence.
The Memory Router chooses compact topic memory instead of flooding every worker with the whole project history.
Short-lived workers perform bounded tasks with only the tools and context required for that role.
Tests, validators and structured checks decide whether the result satisfies the actual task contract.
Governance policy chooses accept, retry, escalate or stop instead of allowing an unbounded repair loop.
Runtime traces expose worker activity, decisions, costs, validations, retries and governance outcomes.
Useful memory and skills can be retained selectively while obsolete context is rotated instead of accumulating forever.
Tenrec separates project persistence from prompt context. A small Memory Router decides which compact memory blocks are relevant to the current task.
Evaluation produces evidence. Governance decides what happens next. The runtime does not let a worker simply keep trying until tokens run out.
Tenrec exposes execution traces, quality signals and governance outcomes so AI software work can be debugged like software.
Tenrec separates learned recognition from runtime control so each layer can be tested independently.
Tenrec keeps project state persistent while short-lived specialized workers operate with selective memory, deterministic evaluation, governance and full execution visibility.