Ownership

Authored and generated files

The sources manifest in project.json assigns each recorded file either authored or generated ownership. Generation creates missing authored scaffolds and preserves existing authored files. It replaces generated files to reflect the graph and dependency pins; a local modification to a recorded generated file blocks this operation.

Compiler-created Python extension points use ● impl.py. Entity declarations and collection packages use generated ◆ __init__.py files. Workflows receive authored ● requirements.txt; their profiles, sessions, and bindings are generated from project.json.

File color convention

Throughout the documentation, file ownership is denoted by green ● user/authored and blue ◆ generated/system-managed.

	● User/authored files	◆ Generated/system-managed files
Purpose	Define domain types, visit behavior, prompts, and dependencies	Declare typed interfaces, adapters, graph connections, resources, and package metadata
Editing	Edit normally in VS Code	Do not edit directly; local modifications block generation
Lifecycle	Preserved by generation	May be replaced or deleted when the graph changes

Authored behavior is Python 3.12. Additional helper modules and resources may be placed outside generated paths. Renaming can move authored files and rewrite structural references; deletion can remove the files owned by a deleted entity. These operations are distinct from generation.