[GTrunSec]

The public configuration is now one programs.deterministic-engineering.languages..{enable,settings} tree, maintained in root config.ss and illustrated by examples/programs.ss. C and C++ are supported by real maintained Profiles; both are disabled by default. The old paired default/disabled Examples are removed.

Downstream Modules use Yuanxu's existing config-defaults to recursively compose POO values. Omitted fields inherit, explicit false remains false, and scalar/list values replace their field. Native sealed Records validate the final configuration. No local recursive merge, configuration loader, dispatch registry, compatibility facade or application Runtime is added.

Language projections read the final Scope's Profile map and configuration. They select maintained Profiles, reject cross-language selection and derive configured method scopes. A downstream POO Profile contribution can be selected through the same interface. Effective deadlines are part of the plan and method evidence identity; the maximum remains 45 seconds, while users can tighten it.

Validation:

• Native root build exits 0 under the unchanged 180-second fence.
• Six configuration cases pass, including actual user values, inherited sibling defaults, partial overrides, explicit false, typo rejection and all previous selection controls.
• The complete eight-case actual C/C++/ASCENT suite remains passing with natural exit.
• The native consumer case imports the actual unified Example, compiles/runs real C and C++ subjects and registers/queries their privately issued observations in ASCENT.
• It checks downstream POO Profile extension, cross-language refusal, C-only disable, old-owner/result refusal, retained historical witnesses and still-enabled C++ settings/plan.
• Reusing a result from a 30-second method context in a 25-second usage produces mismatch and no support while retaining the witness.
• Native package metadata and compiled Config/Type/root/ASCENT ABI qualification pass, including original closure negative controls and regular artifacts before import.
• English Org 10.149 defines the current contract; 10.148 marks prior flat interfaces as superseded. D2 and source-bound TS/Playwright/ELK/Sharp figures are synchronized with lossless PNG/WebP checks.
• Local REUSE lint passes 778/778 files. Scheme tests remain under t/*-test.ss; each Scheme process retains the 2 GiB heap limit, existing process deadlines and machine-derived build concurrency.

The single root dependency remains the locally qualified AI Agentic Lab revision 558e9bd5b8acf1ec644c74c9621007a3695de636. Its native closure and optional Core source gitlink remain distinct. The newer Parent PR #34 cohort is audited but not promoted without fresh installation/build/consumer evidence.

Remaining gates:

• Complete cold dependency installation, including the historical Orgize timeout, is not qualified. A native-generated manifest and incremental package success do not establish every Parent feature.
• Full remote exact-head CI remains incomplete. At b7ad4e0, REUSE passed and both render platforms passed typecheck/core/export tests but failed the example regression on retired formation source references. The follow-up renderer migration now updates those references and their declaration/host responsibility semantics; exact-head remote validation remains required.
• Disabled language data does not prove namespace absence or zero compiler demand. A shared configuration-file change may invalidate an old owner even when one language's values are unchanged; retained historical evidence is not automatic current receipt admission.
• Invoked executable entry bytes and declared sources/plans/artifacts are bound. Complete backend compiler, SDK/header/shared-library attestation and arbitrary helper hot reload are not established.
• Independent consumer reuse shares an identical physical implementation capture; unrelated implementations are not equated.

The PR remains draft. Library declarations, Types, Profiles, finite rules and evidence contracts stay here; transport, providers, approval and application recovery stay with external consuming systems.

Renderer follow-up (4f43d48):

• Views 90.02, 90.132, 90.133 and 90.138 now reference maintained flat Library Modules and describe design-only declarations/input bindings, with acquisition and execution owned by consuming hosts. No capture executor or runtime has been reintroduced.
• Existing TypeScript/Chromium export regenerates published figures, comparisons and source receipts. All 373 source bindings across the affected view family match current files.
• Local typecheck, 82 core tests, 38 browser/export tests, 6 example tests (104 assertions), and REUSE 778/778 pass. Chromium tests require normal macOS process permissions; the rejected sandbox launch is retained separately from the successful native run.
• Full cold dependency installation and exact-head remote CI remain unqualified until independently observed.

Exact-head follow-up at 4f43d48:

• macOS renderer workflow passes all steps, including the Git-installed package consumer. REUSE passes.
• Linux attempt 1 fails before tests during Chromium system-dependency installation: Ubuntu mirror DNS resolution errors. Only the failed Linux job is retried; the workflow and its deadlines are unchanged.
• The further native build-projection consumer audit fails before assertions in Yuanxu read-projection's generated POO import. An incremental Core package build returning zero did not resolve that failure.
• A native SDK Core clean followed by a real rebuild exceeds the unchanged 180-second deadline (exit 124). This is failed cold-build evidence, not acceptance; incremental artifact recovery is tracked separately. No dependency, assertion or manifest is fabricated or removed.

Native diagnostic refinement:

• Incremental recovery after the failed clean rebuild finishes with exit 0; it does not replace the exit-124 cold-build result.
• The unchanged formation build-projection test still fails at the Core generated import after recovery.
• An independently compiled minimal native consumer of POO slot-read-dependencies imports successfully in a fresh process. The current evidence therefore narrows investigation to the Core build-projection loading/expansion context; it does not establish a general POO export ABI defect or a stale-product-only cause.