Flatfile Agential Resource System Blueprint
What this is
A FlatfileAgentialResourceSystemBlueprint is an AgentialRelationsSystemBlueprint within a FlatfileAgentialResourceSystem.
In the flatfile substrate, a blueprint is a spec subdirectory that has colocated skills, SHACL shapes governing those skills, and runbooks that operate on the scope. The specification is complete. No context files are present — the scope has not yet declared an agent community, has no governing soul document, and is not live.
A FlatfileAgentialResourceSystemBlueprint MUST satisfy all requirements of FlatfileAgentialResourceSystemOutpost.
File structure
spec/{id}/
{id}.md # the entity's own spec file
skills/ # named operations
{skill-id}.md
...
runbooks/ # structural procedures operating on this scope
{runbook-id}.md
...
shacl/
{id}-*.ttl # shapes governing which sub-configurations are valid
No context files. No AGENTS.md, no SOUL.md, no INBOX.md, no PLANS.md, no IDEAS.md, no MEMORY.md.
A FlatfileAgentialResourceSystemBlueprint MUST have at least one SHACL shape targeting its operations and a runbooks/ subdirectory with at least one runbook operating on this scope.
It CANNOT have any of the six locale context files (AGENTS.md, SOUL.md, INBOX.md, PLANS.md, IDEAS.md, MEMORY.md).
The presence of SHACL shapes (condition 5) and runbooks (condition 6) alongside skills (condition 4) is what distinguishes a blueprint from an outpost. An outpost has skills but no shapes and no runbooks. A blueprint has all three.
What a blueprint is not
A blueprint is not a locale with files missing. It is an entity at a valid and complete depth in the depth filtration: fully constituted as a specification, appropriately without an agent community because none has been declared yet.
Growing past blueprint
A FARS blueprint grows into a FlatfileAgentialResourceSystemCharter by the addition of AGENTS.md: the declaration of who acts in this scope and under what operational policies.