# Crucible and default-import work map

2026-10-31 — baseline PyCForge 1.3.78.

The [coordinated roadmap](ROADMAP.md) governs priorities, progression and release
gates across PCFC11, Crucible, the bundled conversion imports and the SDK.
This file maps conversion work to that plan; it is not a competing schedule.

The 1.3.78 reliability increment makes definition navigation, source outlines
and folding recognize conversion declarations through the existing shared
syntax contract. It also records practical and large-function native pipeline
measurements. Sum/mean remains the next new numerical capability; the current
math, NumPy and JSON operation sets and SDK contracts are unchanged.

| Shared work | Practical default-import use | Required dependency or evidence |
| --- | --- | --- |
| Numeric semantics and reductions | Deepen math and one-dimensional NumPy; sum/mean are the preferred next addition after the baseline audit. | Explicit accumulation/rounding, empty/overflow/error policy; boundary/reference cases and native compiler checks. |
| Call binding and source diagnostics | Consistent supported signatures and useful rejection in every package. | Evaluation once in source order; exact optional/named argument profiles; preserved failure categories. |
| Strings, containers and structured values | JSON round trips and composition with ordinary application functions and records. | Encoding, numeric/depth/size limits, ownership, allocation rollback and module-boundary tests. |
| Array representation | Owned contiguous two-dimensional arrays, followed by separately gated views/strides, dtypes and broadcasting. | Shape/layout/index arithmetic first; explicit copying/aliasing and lifetime contracts; operations qualify together. |
| Runtime memory and native resources | Reliable long-running use of all allocation-backed imports. | Generated roots, safe points and helper scratch; deterministic resource release; no GC-dependent finalizers. |
| Generated C quality and performance | Smaller, predictable conversion/compile costs and reusable kernels. | Phase measurements, compiler comparisons, bounded changes and preserved observable semantics. |

For each row, audit existing behavior before declaring a gap. Keep Typed and
Runtime coverage distinct. Default imports use reusable engine services;
independent SDK namespaces must qualify those same services. Engine-owned
metadata carries additive choices when the unchanged SDK can consume them.

Current contracts are in
[framework 0.9](specifications/PyCForge-SDK-Framework-0.9.md),
[framework 0.8](specifications/PyCForge-SDK-Framework-0.8.md),
[workbench 1.0](specifications/PyCForge-SDK-Workbench-1.0.md) and
[Runtime memory](specifications/runtime_memory_1_3_72.md).
These specify current behavior; the work map above describes future progression.

The full previous conversion roadmap and release-specific entries are
[preserved unchanged](specifications/roadmap-history/CONVERSION_ROADMAP-before-coordination-2026-10-31.txt).
They contain earlier assumptions and completed capabilities. Consult them for
history and regression leads, not as authority to repeat work or restore old
restrictions. The coordinated roadmap supplies the current promotion gates.
