PRODUCT REFERENCE
The package release and converter surfaces have separate identities. PyCForge {{APPLICATION_VERSION}} retains the Phase 16 base schemas and renderer while adding authenticated 1.0.1 set-admission and membership rules to the installed rule manifest.
| Surface | Active value |
|---|---|
| Application package | {{APPLICATION_VERSION}} |
| Converter contract | 0.16.0 |
| Rule set | phase16-scope-loop-file-v0.16.0 |
| Set capability rules | pycforge101.container.set_literal@1.0.1 and pycforge101.container.set_membership@1.0.1 |
| Renderer | c-renderer-v0.16.0 |
| Runtime policy | phase16-bounded-runtime-v0.16.0 |
| Conversion plan | conversion-plan/0.16.0 |
| C IR | c-ir/0.16.0 |
| Generated artifact | generated-c/0.16.0 |
| Conversion summary | pycforge.conversion-summary/0.16.0 |
| Decision trace | pycforge.decision-trace/0.16.0 |
| Result envelope | 0.5 |
| Desktop worker protocol | pycforge.worker-protocol/0.2 |
| Workspace | pycforge-workspace/0.7 |
| Action registry | pycforge.action-registry/0.5 |
| Visual system | pycforge.visual-system/0.4 |
| Presentation settings | schema 3 |
The active Phase 16 profile cumulatively carries typed functions and
control flow, direct source calls, fixed containers, explicit module bundles,
immutable static records, bounded floor arithmetic, conditional temporary
regions, exact keyword calls, required keyword-only calls, selective
branch-defined scalar publication, complete admitted loop-else,
overflow-safe range updates, and bounded UTF-8 file sessions.
Version 1.0.1 additionally admits fixed numeric and Boolean set literals
with proved in/not in membership. The rule-registry
manifest fingerprint and package version distinguish this additive capability
without rewriting the stable Phase 16 C-IR or rendering schemas.
Explicit historical rule-set and renderer pairs remain requestable through the advanced Python API for compatibility: frontend 0.3, planning 0.5, first slice 0.6, control flow 0.8, functions and calls 0.9, containers 0.11, modules 0.12, records 0.13, and numeric or call profiles 0.14 through 0.14.3. Those profiles do not silently acquire later semantics; the 1.0.1 set rules are enabled only for the active Phase 16 base profile.