Project Forge Dependency Diagram

This Markdown-only dependency map records the intended direction for forge-core. It follows FORGE-100’s unidirectional architecture, FORGE-101’s composition boundaries, FORGE-102’s staged delivery, and FORGE-103’s requirement that standards be explicit before implementation begins.

contracts
  ^  ^  ^  ^  ^  ^  ^  ^
  |  |  |  |  |  |  |  |
core
composition
configuration
identity
registry
knowledge
publication
storage
utilities

tests may reference every area for verification only.

Initial rules:

contracts must not depend on implementation areas.
core may depend on contracts only.
composition may depend on contracts, core, configuration, identity, registry, knowledge, publication, and storage as specifications mature.
utilities must remain domain-neutral and must not create hidden architectural dependencies.
tests may depend on any area for verification, but must not become a runtime dependency.