Program structure
Platform spec area
Program structure
No architecture decision records under adr/ for this feature yet. Standard features must
publish at least one ADR or keep a ## Decisions summary on the hub.
- Code style and naming Language-level naming and style conventions that affect readability and tooling consistency.
- extend type Type extension syntax replacing impl blocks; public members only, full type scope access.
- Modules and visibility File layout, `public`/`internal` boundaries, and how packages compose. The driver and package manager use the same module graph the typechecker sees.
- Name resolution Scopes, imports, and shadowing tie syntax to symbols. Diagnostics for unresolved names must cite these rules verbatim.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
scope | yes | yes |
features | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Scope
Modules, paths, and name resolution across compilation units.
Feature index
Use the tiles below for normative feature contracts in this area.
Features
- Code style and namingLanguage-level naming and style conventions that affect readability and tooling consistency.
- extend typeType extension syntax replacing impl blocks; public members only, full type scope access.
- Modules and visibilityFile layout, `public`/`internal` boundaries, and how packages compose. The driver and package manager use the same module graph the typechecker sees.
- Name resolutionScopes, imports, and shadowing tie syntax to symbols. Diagnostics for unresolved names must cite these rules verbatim.