Ownership ratified • Local implementation 0.1.0 • Unpublished

ContextForge links context and explains what belongs.

Agents need policy, facts, memory, behavior and a mission together without losing the boundaries between them. ContextForge assembles those explicit inputs into a deterministic context bundle.

The first local implementation explains each inclusion and omission: which dependency required an item and whether a size budget affected it. Its tests use explicit synthetic inputs; live domain adapters remain future work.

Decision and implementation evidence Stack context

Pure linking flow

Resolved Lex policy + typed context inputs
                    |
                    v
             ContextForge
                    |
                    v
      Context bundle + explanations

          authorizesExecution: false

One responsibility

Preserve the input boundaries

Lex resolves policy. Domain owners supply facts, behavior, memory, identity, mission and capability requirements. ContextForge links explicit values without redefining their meaning.

Keep required context together

Required dependencies come before relevance scoring or size reduction. Missing mandatory inputs remain visible and block readiness; optional material can be minimized.

Make selection explainable

The bundle records stable explanations for inclusion, exclusion and budget selection. Determinism is tested across processes on identical explicit inputs.

Current status

Ownership and input contracts are ratified in Lex #837. The first local implementation, LINK-1B1 version 0.1.0, passed 17 contract tests, type and import checks, and an independent packed-consumer check. The package remains private and unpublished, with no public source repository, live domain adapter or LexRunner consumer.

The core performs no provider calls, storage access, credential handling or effects. It returns context, diagnostics and explanations; its output cannot authorize execution. Authentication, rich memory text, generated instructions and prompt rendering remain separate future work.

Authorization stays separate

ContextForge does not replace authentication, tenant isolation, protected approvals or effect authorization. LexThority is retained as historical authority research with no active product commitment. Those enforcement responsibilities remain necessary regardless of the name or shape of a future authority component.