onto-mcp 0.3.1 → 0.3.2

package/.onto/processes/shared/target-material-kind-contract.md

@@ -56,7 +56,7 @@ Allowed values:
 | `spreadsheet` | Workbook, sheet, CSV, accounting schedule, formula model, report, or tabular calculation artifact. |
 | `document` | Prose, requirements, policy, guide, report, contract, PDF, DOCX, Markdown, or similar textual artifact. |
 | `database` | Database connection, schema, migration, SQL file, warehouse model, table, view, or query artifact. |
-| `mixed` | Bundle containing more than one material kind. Each member needs its own material classification. |
+| `mixed` | Bundle containing more than one material kind. Each member needs its own material classification; `mixed` itself is not an adapter target. |
 | `unknown` | Runtime cannot classify the material safely. Adapter execution must halt or ask for clarification. |
 
 The axis is separate from:
@@ -77,6 +77,21 @@ The axis is separate from:
 | `reconstruct` | Source profiles, source adapters, source observations, and directive validation must be keyed by `target_material_kind`. |
 | `evolve` | Future adapters must not assume code-product inputs; adapter selection should start from `target_material_kind` as defined in `.onto/processes/evolve/material-kind-adapter-contract.md`. |
 
+### 4.1 Mixed Support Semantics
+
+Because `mixed` is an allowed public value, every process that exposes it must
+also expose one of these support states:
+
+| Support state | Runtime behavior |
+|---|---|
+| `supported_composite` | Classify every member, dispatch only member-specific supported adapters, and preserve cross-material refs as structural refs. |
+| `partial_composite` | Classify every member, observe supported members, record unsupported members and downstream authority impact. |
+| `unsupported` | Halt or ask for clarification before adapter dispatch with a stable unsupported reason. |
+| `reserved_future` | Treat `mixed` as non-executable vocabulary and do not expose it as a runnable path. |
+
+No process may dispatch a single generic `mixed` adapter. Semantic
+cross-material interpretation belongs to the LLM after runtime observation.
+
 ## 5. Artifact Contract Additions
 
 | Artifact | Required change |
@@ -120,7 +135,8 @@ Runtime must validate:
 
 - `target_material_kind` is one of the allowed values
 - `unknown` does not dispatch a material adapter
-- `mixed` records per-member material kinds
+- `mixed` records per-member material kinds and one of the support states in
+  section 4.1 before adapter dispatch
 - unsupported formats halt or degrade explicitly
 - source observations do not claim ontology facts such as entity, relation,
   business rule, aggregate root, or policy meaning

package/.onto/roles/axiology.md

@@ -61,12 +61,17 @@
 
 현재 lens set 에 빠진 purpose-critical 관점을 이 lens 가 발견하면 여기서 직접 제안한다. `synthesize` 는 이 제안을 보존할 수 있으나 독자적으로 발명할 수 없다. 이 slot 은 axiology 만 사용할 수 있는 의도적 canonical asymmetry 이다.
 
+이 slot 은 domain concern 을 active lens 로 승격하는 장치가 아니다. domain 문서의 concern
+tag, CQ, case evidence 는 원칙적으로 기존 lens/CQ/domain-rule 경로로 소비된다.
+New Perspectives 는 "현재 domain 이 새 lens 를 원한다"는 뜻이 아니라, review process
+governance 에서 별도로 검토할 수 있는 목적상 미커버 관찰을 보존하는 출력이다.
+
 New Perspectives 제안 시 최소 필수 필드:
 
 1. **trigger condition** — 제안을 촉발한 증거 (대상 · 관찰 · authority 미커버 영역)
 2. **proposed perspective** — 무엇을 평가할 것인가 (1~2 문장 perspective 요약)
-3. **insufficiency argument** — 기존 9 lens 각각이 이 관점을 왜 커버하지 못하는지 명시
-4. **intended receiving seat** — 제안이 착지해야 할 위치 (현재 review 의 `synthesize` 보존 / 후속 lens governance / axiology 내부 sub-check 등). 착지 seat 미지정 제안은 orphaned 로 간주하여 `synthesize` 가 거부할 수 있다
+3. **insufficiency argument** — 기존 9 lens, CQ, domain rule 경로가 이 관찰을 왜 충분히 커버하지 못하는지 명시
+4. **intended receiving seat** — 제안이 착지해야 할 위치 (현재 review 의 `synthesize` 보존 / 기존 lens·CQ·domain rule 보강 / 후속 lens governance / axiology 내부 sub-check 등). 착지 seat 미지정 제안은 orphaned 로 간주하여 `synthesize` 가 거부할 수 있다
 
 New Perspectives 제안은 현재 리뷰 실행의 active lens set 을 변경하지 않는다. 실제 lens set 확장은 별도 governance 경로를 통한다.
 

package/AGENTS.md

@@ -61,8 +61,9 @@ target material 관련 작업 시 추가로 읽을 문서:
 
 1. [reconstruct-boundary-contract.md](/Users/kangmin/cowork/onto-mcp/.onto/processes/reconstruct/reconstruct-boundary-contract.md)
 2. [reconstruct-execution-ux-contract.md](/Users/kangmin/cowork/onto-mcp/.onto/processes/reconstruct/reconstruct-execution-ux-contract.md)
-3. [source-profile-contract.md](/Users/kangmin/cowork/onto-mcp/.onto/processes/reconstruct/source-profile-contract.md)
-4. selected source profile under `.onto/processes/reconstruct/source-profiles/`
+3. [top-level-concept-discovery-contract.md](/Users/kangmin/cowork/onto-mcp/.onto/processes/reconstruct/top-level-concept-discovery-contract.md)
+4. [source-profile-contract.md](/Users/kangmin/cowork/onto-mcp/.onto/processes/reconstruct/source-profile-contract.md)
+5. selected source profile under `.onto/processes/reconstruct/source-profiles/`
 
 ---
 

package/README.md

@@ -36,17 +36,17 @@ cross-process goal contract lives at
 
 `reconstruct` now has a current design contract under
 `.onto/processes/reconstruct/`, material-aware runtime helpers, and a bounded
-happy-path runner. The runner classifies target material, writes source
-observations, accepts pluggable LLM-owned directive authors and confirmation
-providers, validates evidence refs, computes deterministic metrics, and writes
+direct-call integral runner. The runner classifies target material, expands
+directory targets into per-member source observations, writes the initial source
+frontier, runs reconstruct lens judgments and exploration synthesis through a
+configured LLM provider, validates evidence refs, computes deterministic metrics, and writes
 `final-output.md`, `reconstruct-run-manifest.yaml`, and the primary
 `reconstruct-record.yaml`. Code is the first fixture; the runner path is shared
 with spreadsheet/document/database material through source profiles and
-material-specific observers. The current public run path is an explicit mock
-semantic/confirmation post-Seed artifact loop. It implements claim realization,
-confirmation validation, competency-question assessment, failure classification,
-revision proposal, metrics/status projection, and artifact-tethered final
-output; domain context selection remains deferred.
+material-specific observers. The current public run path defaults to
+`direct_call` semantic authoring and host-mediated confirmation. It fails loud
+when provider/model/credentials, LLM-authored artifact shape, or runtime gates
+are invalid; domain context selection remains deferred.
 `evolve` has a future material-kind adapter contract at
 `.onto/processes/evolve/material-kind-adapter-contract.md`, but no active
 runtime or MCP tool. `learn` and `govern` remain separate design slices.
@@ -87,7 +87,7 @@ Available MCP tools:
 | `onto.list_source_profiles` | List reconstruct source profiles |
 | `onto.observe_source` | Materialize reconstruct material profile, inventory, source observations, and initial record |
 | `onto.validate_reconstruct_directive` | Validate LLM-authored reconstruct directive files |
-| `onto.reconstruct` | Run the material-aware reconstruct post-Seed loop with explicit mock semantic/confirmation realization |
+| `onto.reconstruct` | Run the material-aware direct-call reconstruct path with runtime validation gates |
 | `onto.reconstruct_status` | Read reconstruct session status, progress, counts, and artifact refs |
 | `onto.reconstruct_result` | Read `reconstruct-record.yaml`, run manifest, progress projection, and final output |
 
@@ -104,18 +104,15 @@ Minimal reconstruct MCP call shape:
     "projectRoot": "/path/to/project",
     "targetRefs": ["src/example.ts"],
     "intent": "Create a bounded reconstruct Seed from this target.",
-    "sessionRoot": ".onto/reconstruct/example-run",
-    "semanticAuthorRealization": "mock",
-    "confirmationProviderRealization": "mock"
+    "sessionRoot": ".onto/reconstruct/example-run"
   }
 }
 ```
 
-`semanticAuthorRealization` and `confirmationProviderRealization` are required
-so completed reconstruct runs are explicit about their current mock semantics.
-Today this proves the material-aware post-Seed artifact loop, runtime gates, and
-MCP surface. It does not claim live host-LLM semantic authorship or live
-user-mediated confirmation.
+`semanticAuthorRealization` and `confirmationProviderRealization` default to
+`direct_call`. Configure `.onto/settings.json` or user `~/.onto/settings.json`
+with an `llm` provider/model before running. Test-only mock helpers are not
+product completion evidence.
 
 Repository-local development harness:
 
@@ -238,44 +235,53 @@ Primary outputs:
 
 A reconstruct session writes artifacts under `.onto/reconstruct/<session-id>/`.
 
-Implemented mock-authored, runtime-gated outputs:
+Implemented direct-call, runtime-gated outputs:
 
 | Artifact | Owner | Purpose |
 |---|---|---|
 | `target-material-profile.yaml` | runtime | detected `target_material_kind`, support status, and selected source profiles |
 | `source-inventory.yaml` | runtime | material-specific inventory units and scan boundary |
+| `initial-source-frontier.yaml` | runtime | first observation frontier derived from inventory |
 | `source-observations.yaml` | runtime | structural observations with stable evidence ids |
-| `source-observation-directive.yaml` | mock/host author | selected observations for evidence use |
+| `source-observation-directive.yaml` | host LLM author | selected observations for evidence use |
 | `source-observation-directive-validation.yaml` | runtime | validation of selected observation refs |
-| `seed-candidate.yaml` | mock/host author | evidence-backed Seed candidate |
-| `seed-candidate-validation.yaml` | runtime | Seed claim and evidence-ref validation |
-| `claim-realization-map.yaml` | mock/host author | claim-level evidence stance |
+| `rounds/<round-id>/lens-judgments/*.yaml` | host LLM author | reconstruct lens judgments over trusted observations |
+| `rounds/<round-id>/exploration-synthesis.yaml` | host LLM author | integrated gaps and next-source needs |
+| `rounds/<round-id>/source-frontier.yaml` | host LLM author | requested next source refs or no-next-frontier rationale |
+| `rounds/<round-id>/source-frontier-validation.yaml` | runtime | boundary, duplicate, and inventory validation for the frontier |
+| `seed-candidate.yaml` | host LLM author | evidence-backed Seed candidate with separate `claim_id` and user-facing `name` |
+| `seed-candidate-validation.yaml` | runtime | Seed claim name, shape, and evidence-ref validation |
+| `claim-realization-map.yaml` | host LLM author | claim-level evidence stance |
 | `claim-realization-map-validation.yaml` | runtime | claim id, stance enum, and evidence linkage validation |
-| `seed-confirmation.yaml` | mock/host/user mediated | accepted, rejected, partial, or deferred Seed confirmation |
+| `seed-confirmation.yaml` | host/user mediated | accepted, rejected, partial, or deferred Seed confirmation |
 | `seed-confirmation-validation.yaml` | runtime | confirmation transition validation and derived claim sets |
-| `competency-questions.yaml` | mock/host author | questions linked to confirmed claims |
-| `competency-questions-validation.yaml` | runtime | CQ id, claim-link, and evidence validation |
-| `competency-question-assessment.yaml` | mock/host author | answer status for every authoritative CQ |
+| `competency-questions.yaml` | host LLM author | questions linked to confirmed claims |
+| `competency-questions-validation.yaml` | runtime | CQ id, eligible-claim coverage, claim-link, and evidence validation |
+| `competency-question-assessment.yaml` | host LLM author | answer status for every authoritative CQ |
 | `competency-question-assessment-validation.yaml` | runtime | exactly-once CQ assessment validation |
-| `failure-classification.yaml` | mock/host author | material failure and gap classification |
+| `failure-classification.yaml` | host LLM author | material failure and gap classification |
 | `failure-classification-validation.yaml` | runtime | failure enum, linkage, and materiality validation |
-| `revision-proposal.yaml` | mock/host author | bounded revision/deferral proposals |
+| `revision-proposal.yaml` | host LLM author | bounded revision/deferral proposals |
 | `revision-proposal-validation.yaml` | runtime | proposal id, target, action, and regression guard validation |
 | `reconstruct-metrics.yaml` | runtime | deterministic counts, unresolved/deferred counts, and pass rate |
-| `stop-decision.yaml` | mock/host author | stop, continue, or ask-user decision based on metrics |
-| `final-output.md` | mock/host author | user-facing result grounded in artifacts and provenance-checked by runtime |
+| `stop-decision.yaml` | host LLM author | stop, continue, or ask-user decision based on metrics |
+| `final-output.md` | host LLM author | user-facing result grounded in artifacts and provenance-checked by runtime |
 | `reconstruct-run-manifest.yaml` | runtime | step refs, `performed_by` provenance, execution profile, and happy-path scope |
 | `reconstruct-record.yaml` | runtime | primary structured reconstruct artifact |
 
 Current deferred reconstruct artifacts are recorded in
 `reconstruct-run-manifest.yaml` under `happy_path_scope.deferred_artifacts`:
 `domain_context_selection` and `domain_context_selection_validation`. Those
-require additional domain selection semantics and are outside the current mock
-path.
+require additional domain selection semantics and are outside the current
+direct-call path.
 
-The post-Seed design contract also defines validation artifacts for those
+The reconstruct design contract also defines validation artifacts for those
 stages, stable reconstruct stage ids, cross-artifact id authority, and progress
 UX expectations in `.onto/processes/reconstruct/reconstruct-execution-ux-contract.md`.
+Seed discovery is further constrained by
+`.onto/processes/reconstruct/top-level-concept-discovery-contract.md`, which
+defines the Seed as a purpose-relative top-level concept discovery artifact
+rather than a full ontology or broad claim ledger.
 
 ## Repository Map
 

package/dist/core-api/reconstruct-api.js

@@ -5,7 +5,9 @@ import { parse as parseYaml } from "yaml";
 import { RECONSTRUCT_STAGE_IDS, } from "../core-runtime/reconstruct/artifact-types.js";
 import { materializeReconstructPreparationArtifacts, } from "../core-runtime/reconstruct/materialize-preparation.js";
 import { assembleReconstructRecord, } from "../core-runtime/reconstruct/record.js";
-import { createAutoAcceptReconstructConfirmationProvider, createMockReconstructDirectiveAuthor, runReconstruct, } from "../core-runtime/reconstruct/run.js";
+import { createAutoAcceptReconstructConfirmationProvider, createDirectCallReconstructConfirmationProvider, createDirectCallReconstructDirectiveAuthor, createMockReconstructDirectiveAuthor, runReconstruct, } from "../core-runtime/reconstruct/run.js";
+import { resolveSettingsChain, } from "../core-runtime/discovery/settings-chain.js";
+import { resolveLlmProviderConfig, } from "../core-runtime/llm/llm-caller.js";
 import { writeSeedCandidateValidationArtifact, } from "../core-runtime/reconstruct/seed-candidate-validation.js";
 import { writeSourceObservationDirectiveValidationArtifact, } from "../core-runtime/reconstruct/directive-validation.js";
 import { loadReconstructSourceProfiles, } from "../core-runtime/reconstruct/source-profiles.js";
@@ -92,11 +94,14 @@ function deriveReconstructProgress(args) {
                         : "pending",
             owner: step?.owner ?? null,
             artifactRefs: step?.artifact_refs ?? [],
+            reason: step?.reason ?? null,
+            authorityImpact: step?.authority_impact ?? null,
         };
     });
     const lastReachedStage = [...stages].reverse().find((stage) => stage.state !== "pending") ??
         stages[0];
     return {
+        executionProfile: args.runManifest?.execution_profile ?? null,
         currentStageId: lastReachedStage.stageId,
         stageCount: RECONSTRUCT_STAGE_IDS.length,
         liveness: {
@@ -133,6 +138,7 @@ function recordArtifactRefsFromPreparation(refs) {
     return {
         target_material_profile: refs.target_material_profile,
         source_inventory: refs.source_inventory,
+        initial_source_frontier: refs.initial_source_frontier,
         source_observations: refs.source_observations,
     };
 }
@@ -197,16 +203,27 @@ export function createOntoReconstructCoreApi(options = {}) {
                 ...(ontoHome ? { ontoHome } : {}),
             });
             const targetRefs = request.targetRefs.map((targetRef) => resolveFromBase(projectRoot, targetRef));
+            const settings = await resolveSettingsChain(ontoHome ?? projectRoot, projectRoot);
+            const llmConfig = resolveLlmProviderConfig({ config: settings });
+            const semanticAuthorRealization = request.semanticAuthorRealization ?? "direct_call";
+            const confirmationProviderRealization = request.confirmationProviderRealization ?? "direct_call";
+            const directiveAuthor = semanticAuthorRealization === "mock"
+                ? createMockReconstructDirectiveAuthor()
+                : createDirectCallReconstructDirectiveAuthor({ llmConfig });
+            const confirmationProvider = confirmationProviderRealization === "mock"
+                ? createAutoAcceptReconstructConfirmationProvider()
+                : createDirectCallReconstructConfirmationProvider({ llmConfig });
             return runReconstruct({
                 projectRoot,
                 targetRefs,
                 intent: request.intent,
                 sessionRoot,
                 profilesRoot,
-                semanticAuthorRealization: request.semanticAuthorRealization,
-                confirmationProviderRealization: request.confirmationProviderRealization,
-                directiveAuthor: createMockReconstructDirectiveAuthor(),
-                confirmationProvider: createAutoAcceptReconstructConfirmationProvider(),
+                semanticAuthorRealization,
+                confirmationProviderRealization,
+                directiveAuthor,
+                confirmationProvider,
+                llmConfig,
                 filesystemAllowedRoots: request.filesystemAllowedRoots?.map((root) => resolveFromBase(projectRoot, root)) ??
                     [projectRoot],
             });