irl-dan 05290632a1 rfc 005: package-bounded component resolution ...

Forme's current resolution rules (./name.md, ./name/index.md, .deps/,
registry) force authors into flat layouts or require every internal
module to be externalized as a git dep. Layered/categorized trees
(responsibilities/, services/, services/firehose/, delivery/) have
no resolution path today.

Adds a package-bounded recursive walk as resolution rule (3). The
package root is the nearest ancestor containing .prose/ or prose.lock.
The walk finds .md files by frontmatter name: or filename stem, and
skips .deps/, .prose/, .git/, build dirs, and _-prefixed directories.

Ambiguity across the walk is a hard error — preserves T2 and T16. A
structured path: field on the service entry remains as an escape
hatch for cross-package refs and forced disambiguation.

Convention over configuration: within a package, component names are
unique identifiers. No per-program boilerplate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-21 10:20:07 -07:00

..

001-scheduled-execution.md

docs: make skills and RFCs self-contained

2026-04-20 22:30:20 -04:00

002-feedback-loop-syntax.md

docs: make skills and RFCs self-contained

2026-04-20 22:30:20 -04:00

003-environment-declaration.md

docs: make skills and RFCs self-contained

2026-04-20 22:30:20 -04:00

004-composite-instantiation.md

docs: make skills and RFCs self-contained

2026-04-20 22:30:20 -04:00

005-flexible-component-resolution.md

rfc 005: package-bounded component resolution

2026-04-21 10:20:07 -07:00