| title | Source Package Guides |
|---|---|
| audience | developers, maintainers, contributors |
| prerequisites | contributor architecture guide |
| related | ../architecture.md, ../source-map.md, ../feature-to-code-map.md |
| status | maintained |
| publication | draft |
These pages are the file-level companion to the architecture guide. Read the architecture guide once for the whole flow, then use this table to enter the owner of a change. Do not read the guides as thirteen alternative pipelines: each describes one handoff in the same pipeline.
| Package | Read it when you need to change | Canonical guide |
|---|---|---|
prik.contracts |
public semantic .pyi syntax |
Contracts |
prik.compiler |
compiler profiles, command argv, or native-support installation | Compiler |
prik.preprocessing |
parser input, provenance, includes, or target probes | Preprocessing |
prik.parsers |
Fortran syntax facts or raw .pyi syntax |
Parsers |
prik.semantics |
the shared semantic graph, types, or raw metadata | Semantics |
prik.policy |
completed ownership, projection, lifecycle, or support choices | Policy |
prik.planning |
plan representation, ordering, or backend views | Planning |
prik.codegen |
generated binding, bridge, node, or Python-facade mechanism | Code generation |
prik.printers |
C, Fortran, or .pyi text serialization |
Printers |
prik.pipeline |
wrapper, contract, report, artifact, or build orchestration | Pipeline |
prik.runtime |
imported native handles or bundled native support | Runtime |
prik.naming |
public-name normalization or generated symbols | Naming |
prik.utilities |
a genuinely stage-neutral helper | Utilities |
Each guide answers the same practical questions:
- What does this stage receive and produce?
- Which module owns the behavior I need to change?
- Which classes and functions are the important entrypoints?
- What does each direct-execution example prove?
- Which tests protect that behavior?
The directory tour covers every supported Python module under that package,
including package initializers and nested backend packages. The deferred
C-input frontend is intentionally excluded from the published Fortran route.
Source-tree README.md files remain short orientation notes and link back to
these canonical guides.