[semantic-memory] Expose general semantic ingestion, query, provenance, and bounded world-model projections through native/MCP tools

nsaspy commented

2026-09-08 01:57:03 +00:00

Owner

Parent: #4
Depends on: #5, #6, #7
Related: #8
Upstream: prolog-rlm#388/#392-#396

Goal

Expose the full general semantic-memory feature to agents, Prolog-RLM, editors and other clients through a thin native/MCP surface over the library APIs.

The transport layer owns no memory semantics and no compiler logic.

General tool surface

Provide closed tools equivalent to:

memory_symbolize
memory_projection_status
memory_semantic_query
memory_semantic_projection
memory_semantic_explain
memory_semantic_history
memory_source_expand
memory_symbolize_missing / corpus-ingest trigger where appropriate

Specialized convenience tools such as memory_procedure may exist, but they must sit on the general query substrate and must not fork semantics.

Knowledge coverage

Tools must be able to query/project arbitrary upstream semantic IR classes, including:

entities/types/taxonomy
relations/assertions/negation
rules/defaults/exceptions
procedures/branches/recovery
events/states/time
causal/diagnostic knowledge
quantities/constraints
spatial relations
normative modalities
goals/plans/preferences
attributed claims/conflicts
uncertainty/hypotheses/scenarios
examples/cases
provenance/meta-knowledge
extension vocabulary

Do not expose only facts and procedures while silently dropping other knowledge classes.

Remember and symbolize stay distinct

memory_remember(text)
  -> durable exact source id

memory_symbolize(id)
  -> general semantic projection

A convenience option may request symbolization after remember, but source commit remains independent and authoritative.

Bounded projection

For any goal/query, return only relevant mixed semantic records plus compact provenance refs rather than the full long-term world model.

Example:

Why could service X be failing and what should I try?

may return:

current service facts;
causal/diagnostic rules;
relevant historical event;
applicable procedure/recovery branches;
conflicting claim if present;
constraints/preconditions;
exact source refs.

Source expansion

Any returned semantic record/result can resolve back to exact original source spans when caller read authority permits it.

Prolog-RLM integration

Allow Prolog-RLM hosts to register semantic-memory recall as an optional external capability without reversing dependency direction.

current goal
 -> memory_semantic_projection
 -> bounded general semantic IR
 -> Prolog-RLM retrieval/expert/reasoning
 -> symbolic result
 -> optional conversational rendering

Distinguish clearly:

semantic_compile(text) = compile candidate general knowledge
memory_symbolize(id)   = compile + persist projection for durable source
memory_semantic_query  = reason/query over already remembered semantics

Query result semantics

Transport must preserve structured status and not collapse to prose:

true
explicit_false
unknown
conflicted
unsupported
blocked/error

and carry supporting record/provenance refs, temporal/scenario scope, assumptions/defaults/exceptions, and unresolved conditions.

Authority/security

read/write capabilities remain separate;
knowing record IDs grants no access;
semantic knowledge never grants host execution authority;
remembered normative statements are not authority policy;
no arbitrary executable Prolog accepted;
source expansion obeys read/namespace policy;
symbolization provider usage is visible/bounded;
semantic recall/query works with zero model calls once projections exist;
semantic action terms remain inert unless trusted host code maps them separately.

Acceptance

Native/MCP client remembers and symbolizes heterogeneous text containing multiple knowledge classes.
Query definitions/taxonomy through same general surface.
Query a temporal/event question through same surface.
Query causal/diagnostic + procedure knowledge through same surface.
Query conflicting attributed claims without last-write-wins.
Query safe remembered constraint knowledge.
memory_semantic_projection returns bounded mixed records, not whole store.
memory_semantic_explain resolves derived result to rules/records/source spans.
Source expansion enforces read authority.
Direct library and MCP/native adapter produce equivalent semantics.
Recall/query uses zero model calls once projections exist.
Symbolization reports only actual upstream model/provider usage.
Prolog-RLM fixture consumes remembered general semantic knowledge with original prose absent.
Transport cancellation/error cannot publish partial projection state.
No semantic-memory tool can directly execute remembered action terms.

Refs #4-#8 and prolog-rlm#388/#392-#396.

Parent: #4 Depends on: #5, #6, #7 Related: #8 Upstream: prolog-rlm#388/#392-#396 ## Goal Expose the full general semantic-memory feature to agents, Prolog-RLM, editors and other clients through a thin native/MCP surface over the library APIs. The transport layer owns no memory semantics and no compiler logic. ## General tool surface Provide closed tools equivalent to: ```text memory_symbolize memory_projection_status memory_semantic_query memory_semantic_projection memory_semantic_explain memory_semantic_history memory_source_expand memory_symbolize_missing / corpus-ingest trigger where appropriate ``` Specialized convenience tools such as `memory_procedure` may exist, but they must sit on the general query substrate and must not fork semantics. ## Knowledge coverage Tools must be able to query/project arbitrary upstream semantic IR classes, including: ```text entities/types/taxonomy relations/assertions/negation rules/defaults/exceptions procedures/branches/recovery events/states/time causal/diagnostic knowledge quantities/constraints spatial relations normative modalities goals/plans/preferences attributed claims/conflicts uncertainty/hypotheses/scenarios examples/cases provenance/meta-knowledge extension vocabulary ``` Do not expose only `facts` and `procedures` while silently dropping other knowledge classes. ## Remember and symbolize stay distinct ```text memory_remember(text) -> durable exact source id memory_symbolize(id) -> general semantic projection ``` A convenience option may request symbolization after remember, but source commit remains independent and authoritative. ## Bounded projection For any goal/query, return only relevant mixed semantic records plus compact provenance refs rather than the full long-term world model. Example: ```text Why could service X be failing and what should I try? ``` may return: - current service facts; - causal/diagnostic rules; - relevant historical event; - applicable procedure/recovery branches; - conflicting claim if present; - constraints/preconditions; - exact source refs. ## Source expansion Any returned semantic record/result can resolve back to exact original source spans when caller read authority permits it. ## Prolog-RLM integration Allow Prolog-RLM hosts to register semantic-memory recall as an optional external capability without reversing dependency direction. ```text current goal -> memory_semantic_projection -> bounded general semantic IR -> Prolog-RLM retrieval/expert/reasoning -> symbolic result -> optional conversational rendering ``` Distinguish clearly: ```text semantic_compile(text) = compile candidate general knowledge memory_symbolize(id) = compile + persist projection for durable source memory_semantic_query = reason/query over already remembered semantics ``` ## Query result semantics Transport must preserve structured status and not collapse to prose: ```text true explicit_false unknown conflicted unsupported blocked/error ``` and carry supporting record/provenance refs, temporal/scenario scope, assumptions/defaults/exceptions, and unresolved conditions. ## Authority/security - read/write capabilities remain separate; - knowing record IDs grants no access; - semantic knowledge never grants host execution authority; - remembered normative statements are not authority policy; - no arbitrary executable Prolog accepted; - source expansion obeys read/namespace policy; - symbolization provider usage is visible/bounded; - semantic recall/query works with zero model calls once projections exist; - semantic action terms remain inert unless trusted host code maps them separately. ## Acceptance - [ ] Native/MCP client remembers and symbolizes heterogeneous text containing multiple knowledge classes. - [ ] Query definitions/taxonomy through same general surface. - [ ] Query a temporal/event question through same surface. - [ ] Query causal/diagnostic + procedure knowledge through same surface. - [ ] Query conflicting attributed claims without last-write-wins. - [ ] Query safe remembered constraint knowledge. - [ ] `memory_semantic_projection` returns bounded mixed records, not whole store. - [ ] `memory_semantic_explain` resolves derived result to rules/records/source spans. - [ ] Source expansion enforces read authority. - [ ] Direct library and MCP/native adapter produce equivalent semantics. - [ ] Recall/query uses zero model calls once projections exist. - [ ] Symbolization reports only actual upstream model/provider usage. - [ ] Prolog-RLM fixture consumes remembered general semantic knowledge with original prose absent. - [ ] Transport cancellation/error cannot publish partial projection state. - [ ] No semantic-memory tool can directly execute remembered action terms. Refs #4-#8 and prolog-rlm#388/#392-#396.

nsaspy commented

2026-09-08 01:57:31 +00:00

Author

Owner

Machine Spirit #401C handoff — transport must preserve procedural admission/loss semantics

Native/MCP procedure query/projection tools should preserve PIFF status/receipts rather than collapse a remembered procedure to available=true.

For relevant calls expose whether knowledge is merely represented, semantically compatible, execution-projectable, host-bound, capability-available, or currently authority-admissible, plus mapping/PSC versions, declared losses, guarantees/fairness assumptions and unbound actions.

Transport must not turn semantic procedure/action names into executable tools. A caller seeing restart_service, a BPMN service task, BT action leaf or Golog action symbol receives inert semantic data unless trusted host code separately maps it and canonical capability/authority/effect admission succeeds. See prolog-rlm#401 Depth-4C.

## Machine Spirit #401C handoff — transport must preserve procedural admission/loss semantics Native/MCP procedure query/projection tools should preserve PIFF status/receipts rather than collapse a remembered procedure to `available=true`. For relevant calls expose whether knowledge is merely represented, semantically compatible, execution-projectable, host-bound, capability-available, or currently authority-admissible, plus mapping/PSC versions, declared losses, guarantees/fairness assumptions and unbound actions. Transport must not turn semantic procedure/action names into executable tools. A caller seeing `restart_service`, a BPMN service task, BT action leaf or Golog action symbol receives inert semantic data unless trusted host code separately maps it and canonical capability/authority/effect admission succeeds. See prolog-rlm#401 Depth-4C.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Upstream Machine Spirit #401D transport handoff

When procedure knowledge is exposed through native/MCP surfaces, preserve DPEC's status/loss boundaries. A tool result must be able to distinguish a procedure that is merely represented from compatible, projectable, bound, and currently_admissible.

For any host-executable projection, expose compact refs to:

native formalism/procedure version;
PSC/bridge/profile versions;
guarantee/fairness + declared loss;
current binding generation;
conformance receipt;
live prerequisite/admission status.

Do not expose a remembered semantic action as a direct execution tool merely because names match. Transport remains thin; authority/effect admission stays in the host/runtime. Full computational design is on prolog-rlm#401.

## Upstream Machine Spirit #401D transport handoff When procedure knowledge is exposed through native/MCP surfaces, preserve DPEC's status/loss boundaries. A tool result must be able to distinguish a procedure that is merely `represented` from `compatible`, `projectable`, `bound`, and `currently_admissible`. For any host-executable projection, expose compact refs to: - native formalism/procedure version; - PSC/bridge/profile versions; - guarantee/fairness + declared loss; - current binding generation; - conformance receipt; - live prerequisite/admission status. Do not expose a remembered semantic action as a direct execution tool merely because names match. Transport remains thin; authority/effect admission stays in the host/runtime. Full computational design is on prolog-rlm#401.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

MACHINE-SPIRIT #402B handoff — transport status preservation

Native/MCP surfaces must preserve GRIE lifecycle/integrity outcomes rather than flattening them to not-found/false: redacted, quarantined, integrity_failure, replay_degraded, and sanitization partial|pending|blocked|failed where exposed. Redaction/purge is a separately authorized mutation; remembered policy text or semantic actions never grant that authority. Source/history expansion must not leak deleted/private payload through hashes, IDs, provenance or stale caches.

See prolog-rlm#402B for the full contract and B fixtures.

## MACHINE-SPIRIT #402B handoff — transport status preservation Native/MCP surfaces must preserve GRIE lifecycle/integrity outcomes rather than flattening them to not-found/false: `redacted`, `quarantined`, `integrity_failure`, `replay_degraded`, and sanitization `partial|pending|blocked|failed` where exposed. Redaction/purge is a separately authorized mutation; remembered policy text or semantic actions never grant that authority. Source/history expansion must not leak deleted/private payload through hashes, IDs, provenance or stale caches. See prolog-rlm#402B for the full contract and B fixtures.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

MACHINE-SPIRIT #402C handoff — native/MCP federation status preservation

Transport must preserve CLFM's structured federation semantics; no prose/Boolean flattening.

Native/MCP results should be able to expose at least:

logical ledger id / authority domain
per-ledger frontier/checkpoint
federation cut id + completeness
remote receipt/inclusion/consistency status
local admission status
payload/replay/redaction status
causal dependency refs
mapping/link versions
replica/backup/mirror/independent-source class

Hard security boundary:

remote issuer/principal != local principal
remote admission        != local admission
remote policy text      != local authority policy
public receipt          != source-expansion permission
redaction notice        != unrestricted delete capability

A valid SCITT/CT-style receipt must not be rendered as true; it proves the specified integrity/transparency property only. Remote-unavailable/incomplete cuts remain partial outcomes, never ordinary false/unknown collapsed together. Federation query/replay after semantic projections exist remains a zero-model path. Full design: prolog-rlm#402C.

### MACHINE-SPIRIT #402C handoff — native/MCP federation status preservation Transport must preserve CLFM's structured federation semantics; no prose/Boolean flattening. Native/MCP results should be able to expose at least: ```text logical ledger id / authority domain per-ledger frontier/checkpoint federation cut id + completeness remote receipt/inclusion/consistency status local admission status payload/replay/redaction status causal dependency refs mapping/link versions replica/backup/mirror/independent-source class ``` Hard security boundary: ```text remote issuer/principal != local principal remote admission != local admission remote policy text != local authority policy public receipt != source-expansion permission redaction notice != unrestricted delete capability ``` A valid SCITT/CT-style receipt must not be rendered as `true`; it proves the specified integrity/transparency property only. Remote-unavailable/incomplete cuts remain partial outcomes, never ordinary false/unknown collapsed together. Federation query/replay after semantic projections exist remains a zero-model path. Full design: prolog-rlm#402C.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Machine Spirit #402D handoff: native/MCP surfaces must preserve SAFIRE storage state rather than flatten it to prose. Return exact requested/materialized cut, freshness/completeness, integrity/redaction/replay status, and structured resource_limited/partial-remote states. Bounded projection remains mandatory, and already-projected known symbolic tasks must remain capable of model_calls = 0. See prolog-rlm#402 D17/D20-D21/D28/D36/D39.

Machine Spirit #402D handoff: native/MCP surfaces must preserve SAFIRE storage state rather than flatten it to prose. Return exact requested/materialized cut, freshness/completeness, integrity/redaction/replay status, and structured `resource_limited`/partial-remote states. Bounded projection remains mandatory, and already-projected known symbolic tasks must remain capable of `model_calls = 0`. See prolog-rlm#402 D17/D20-D21/D28/D36/D39.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Machine Spirit prolog-rlm#403A handoff — transport preserves projection risk/closure

memory_semantic_projection and related native/MCP surfaces must preserve the TAPS receipt rather than flattening output to prose/top-k records. At minimum expose:

exact cut/freshness + epistemic profile/version;
selected record refs and compact provenance refs;
support_closure;
search_coverage;
unresolved frontier/evidence gaps;
strategy/ranker provenance where soft retrieval was used;
source-expansion refs gated by read authority.

Transport must preserve the distinction that a self-contained support-closed answer may still come from heuristic search coverage. heuristic/partial_backend may never become complete because the adapter returned successfully.

Vector/graph/model ranking remains a candidate sensor, not truth, trust, identity or authority. Exact already-symbolized paths must continue to work with zero model calls. Semantic action terms in a projection remain inert.

Refs prolog-rlm#403 #381 #396 and symbolic-memory#7.

## Machine Spirit prolog-rlm#403A handoff — transport preserves projection risk/closure `memory_semantic_projection` and related native/MCP surfaces must preserve the TAPS receipt rather than flattening output to prose/top-k records. At minimum expose: - exact cut/freshness + epistemic profile/version; - selected record refs and compact provenance refs; - `support_closure`; - `search_coverage`; - unresolved frontier/evidence gaps; - strategy/ranker provenance where soft retrieval was used; - source-expansion refs gated by read authority. Transport must preserve the distinction that a self-contained support-closed answer may still come from heuristic search coverage. `heuristic`/`partial_backend` may never become `complete` because the adapter returned successfully. Vector/graph/model ranking remains a candidate sensor, not truth, trust, identity or authority. Exact already-symbolized paths must continue to work with zero model calls. Semantic action terms in a projection remain inert. Refs prolog-rlm#403 #381 #396 and symbolic-memory#7.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Upstream Machine Spirit #403B transport handoff

prolog-rlm#403B is complete. Native/MCP projection surfaces must not flatten OATH-TAPS bounded-attention results into top_k chunks + prose.

Preserve structured exposure diagnostics including support_closure, search_coverage, opposition_coverage, selection/canonical-revalidation status, freshness/source-independence/identity gaps, sensor disagreement, and exact-cut lineage.

Transport/source text cannot set trusted pinned, mandatory, trust, read-scope, freshness-exception or attention-profile fields. A retrieved document containing prompt/tool instructions remains source semantic content; it never becomes MCP/runtime control or execution authority.

If an external/vector/lexical backend is unavailable or suspicious, surface degraded/partial coverage explicitly. Do not silently substitute a model or report the projection exhaustive. Refs lost-rob0t/prolog-rlm#403 #397 and symbolic-memory#7/#10.

## Upstream Machine Spirit #403B transport handoff `prolog-rlm#403B` is complete. Native/MCP projection surfaces must not flatten OATH-TAPS bounded-attention results into `top_k chunks + prose`. Preserve structured exposure diagnostics including `support_closure`, `search_coverage`, `opposition_coverage`, selection/canonical-revalidation status, freshness/source-independence/identity gaps, sensor disagreement, and exact-cut lineage. Transport/source text cannot set trusted `pinned`, `mandatory`, trust, read-scope, freshness-exception or attention-profile fields. A retrieved document containing prompt/tool instructions remains source semantic content; it never becomes MCP/runtime control or execution authority. If an external/vector/lexical backend is unavailable or suspicious, surface degraded/partial coverage explicitly. Do not silently substitute a model or report the projection exhaustive. Refs lost-rob0t/prolog-rlm#403 #397 and symbolic-memory#7/#10.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

MACHINE-SPIRIT prolog-rlm#403C handoff — transport must not flatten federation

Native/MCP memory_semantic_projection / query results should carry MOSAIC-TAPS interoperability receipts, not just ranked prose/chunks. Preserve backend identity/version, typed local score/rank semantics, cut/snapshot/freshness, translation loss, composition/fusion reason, coverage/opposition gaps, external-vs-canonical admission and scoped threat/robustness claims.

Hard transport invariant:

BM25 score != cosine similarity != graph activation != warrant

Do not serialize them into one generic confidence. Remote query egress also needs host capability/authority admission independent of memory read permission; denied egress should surface as an unavailable/unsatisfied retrieval obligation, not silently broaden authority.

Refs lost-rob0t/prolog-rlm#397 #403 #381 #396 and symbolic-memory#7/#10.

### MACHINE-SPIRIT prolog-rlm#403C handoff — transport must not flatten federation Native/MCP `memory_semantic_projection` / query results should carry MOSAIC-TAPS interoperability receipts, not just ranked prose/chunks. Preserve backend identity/version, typed local score/rank semantics, cut/snapshot/freshness, translation loss, composition/fusion reason, coverage/opposition gaps, external-vs-canonical admission and scoped threat/robustness claims. Hard transport invariant: ```text BM25 score != cosine similarity != graph activation != warrant ``` Do not serialize them into one generic `confidence`. Remote query egress also needs host capability/authority admission independent of memory read permission; denied egress should surface as an unavailable/unsatisfied retrieval obligation, not silently broaden authority. Refs lost-rob0t/prolog-rlm#397 #403 #381 #396 and symbolic-memory#7/#10.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Machine Spirit #403D transport handoff

Native/MCP projection/query surfaces must preserve RACE-TAPS execution semantics instead of flattening them to results + score.

Expose bounded structured fields for exact cut/freshness, support/search/opposition coverage, unsatisfied obligations/gaps, backend-local score/rank provenance, translation/fusion/closure receipts, replay class and resource-limit/cancellation status. Snapshot/cursor drift and remote partial coverage remain visible.

Do not expose optimizer/cache/latency statistics as truth/confidence. Do not let transport retry reorder/tie behavior change normalized results. Query egress authority remains separate from local read authority, including adaptive fallback to remote backends. A known symbolic query through native/MCP must still be provably model_calls = 0.

## Machine Spirit #403D transport handoff Native/MCP projection/query surfaces must preserve RACE-TAPS execution semantics instead of flattening them to `results + score`. Expose bounded structured fields for exact cut/freshness, support/search/opposition coverage, unsatisfied obligations/gaps, backend-local score/rank provenance, translation/fusion/closure receipts, replay class and resource-limit/cancellation status. Snapshot/cursor drift and remote partial coverage remain visible. Do not expose optimizer/cache/latency statistics as truth/confidence. Do not let transport retry reorder/tie behavior change normalized results. Query egress authority remains separate from local read authority, including adaptive fallback to remote backends. A known symbolic query through native/MCP must still be provably `model_calls = 0`.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

MACHINE-SPIRIT #404A handoff — native/MCP learning status

Future native/MCP projections for learned knowledge must preserve structured EPOCH state rather than return an undifferentiated learned=true flag. Expose exact candidate/admitted/suspended/superseded status, learned-object version, promotion/evaluation receipt refs, evidence/counterexample refs and provenance where authorized.

Transport must not offer a shortcut that lets a client/model directly promote arbitrary candidate rules, register executable handlers, widen authority or mutate promotion/VERIFY policy. Any promotion action eventually exposed must be a closed capability-gated operation over an existing candidate and trusted versioned policy.

Ref upstream prolog-rlm#404A EPOCH.

## MACHINE-SPIRIT #404A handoff — native/MCP learning status Future native/MCP projections for learned knowledge must preserve structured EPOCH state rather than return an undifferentiated `learned=true` flag. Expose exact candidate/admitted/suspended/superseded status, learned-object version, promotion/evaluation receipt refs, evidence/counterexample refs and provenance where authorized. Transport must not offer a shortcut that lets a client/model directly promote arbitrary candidate rules, register executable handlers, widen authority or mutate promotion/VERIFY policy. Any promotion action eventually exposed must be a closed capability-gated operation over an existing candidate and trusted versioned policy. Ref upstream prolog-rlm#404A EPOCH.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Machine Spirit #404B / CITADEL-EPOCH native/MCP handoff

Transport must preserve the structured learning lifecycle and evidence limitations rather than flattening to learned=true, promoted=true or confidence=N.

Native/MCP surfaces for learned objects should preserve status/version, promotion receipt refs, applicability epoch/scope, contamination/independence findings, counterexample coverage, drift/calibration state and hard-guard/quarantine reason where present.

No transport caller may assert that evidence is independent, lower a promotion threshold, clear quarantine, or convert a candidate into admitted knowledge solely through request metadata. Those remain trusted #404 policy decisions. Learned semantic actions remain inert with respect to host authority exactly like all other remembered semantic actions. Refs prolog-rlm#404B.

## Machine Spirit #404B / CITADEL-EPOCH native/MCP handoff Transport must preserve the structured learning lifecycle and evidence limitations rather than flattening to `learned=true`, `promoted=true` or `confidence=N`. Native/MCP surfaces for learned objects should preserve status/version, promotion receipt refs, applicability epoch/scope, contamination/independence findings, counterexample coverage, drift/calibration state and hard-guard/quarantine reason where present. No transport caller may assert that evidence is independent, lower a promotion threshold, clear quarantine, or convert a candidate into admitted knowledge solely through request metadata. Those remain trusted #404 policy decisions. Learned semantic actions remain inert with respect to host authority exactly like all other remembered semantic actions. Refs prolog-rlm#404B.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Machine Spirit #404C handoff — transport must preserve learning-transfer semantics

Native/MCP export/import must carry the typed PACT-EPOCH/LAC envelope rather than flattening to learned=true, approved=true, or one confidence score.

Expose at least: artifact kind/version, source authority/promotion attestation, target-local status, applicability/transfer scope, guarantee status, verifier/policy fingerprints, drift/calibration epoch and bounded provenance/dependence refs. Import defaults to foreign_candidate/evidence_only unless target policy locally admits it.

No foreign artifact, attestation or expert composition may import executable handlers, credentials, capabilities or authority. Full design: prolog-rlm#404C.

## Machine Spirit #404C handoff — transport must preserve learning-transfer semantics Native/MCP export/import must carry the typed PACT-EPOCH/LAC envelope rather than flattening to `learned=true`, `approved=true`, or one confidence score. Expose at least: artifact kind/version, source authority/promotion attestation, target-local status, applicability/transfer scope, guarantee status, verifier/policy fingerprints, drift/calibration epoch and bounded provenance/dependence refs. Import defaults to `foreign_candidate`/`evidence_only` unless target policy locally admits it. No foreign artifact, attestation or expert composition may import executable handlers, credentials, capabilities or authority. Full design: prolog-rlm#404C.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Implementation decomposition

#9 remains the canonical native/MCP exposure requirement. The focused implementation slice is #42, under transport epic #18.

#42 must adapt already-working library calls from #20/#22/#28/#29/#31/#34 rather than implement memory semantics in MCP handlers. Direct-library and transport results must normalize equivalently for the same principal/store/frontier.

## Implementation decomposition #9 remains the canonical native/MCP exposure requirement. The focused implementation slice is **#42**, under transport epic #18. #42 must adapt already-working library calls from #20/#22/#28/#29/#31/#34 rather than implement memory semantics in MCP handlers. Direct-library and transport results must normalize equivalently for the same principal/store/frontier.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

MACHINE-SPIRIT #404D transport refinement

Native/MCP transport for learned state must preserve the CLOCKWORK structured contract rather than return prose like validated=true.

Expose exact lifecycle/version, EvaluationSnapshot/profile ref, coverage class, dependence/independence status including unknown, LAC/attestation/transfer refs, promotion decision receipt, drift/suspension state and replay frontier where authorized. Signature validity must remain distinct from semantic/local acceptance.

Transport cannot trigger promotion by changing evaluator/verifier/metric parameters after snapshot freeze, cannot register handlers from candidate payloads, and cannot widen capability/authority. Direct library and transport queries must normalize equivalently. Refs prolog-rlm#404D and #16/#35/#36/#42.

## MACHINE-SPIRIT #404D transport refinement Native/MCP transport for learned state must preserve the CLOCKWORK structured contract rather than return prose like `validated=true`. Expose exact lifecycle/version, EvaluationSnapshot/profile ref, coverage class, dependence/independence status including `unknown`, LAC/attestation/transfer refs, promotion decision receipt, drift/suspension state and replay frontier where authorized. Signature validity must remain distinct from semantic/local acceptance. Transport cannot trigger promotion by changing evaluator/verifier/metric parameters after snapshot freeze, cannot register handlers from candidate payloads, and cannot widen capability/authority. Direct library and transport queries must normalize equivalently. Refs prolog-rlm#404D and #16/#35/#36/#42.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

prolog-rlm#405B AEGIS-MS transport handoff: native/MCP serialization must preserve control-vs-data role, influence/security labels, exact generations and structured stale/blocked states. A transport schema must never upgrade source/model/learned data into trusted control merely because it validates against a closed JSON/schema enum. Direct library and transport paths should fail identically for unendorsed verifier/profile/control identifiers and preserve all AEGIS lineage needed for end-to-end conformance.

prolog-rlm#405B AEGIS-MS transport handoff: native/MCP serialization must preserve control-vs-data role, influence/security labels, exact generations and structured stale/blocked states. A transport schema must never **upgrade** source/model/learned data into trusted control merely because it validates against a closed JSON/schema enum. Direct library and transport paths should fail identically for unendorsed verifier/profile/control identifiers and preserve all AEGIS lineage needed for end-to-end conformance.

nsaspy commented

2026-09-08 01:57:32 +00:00

Author

Owner

Machine Spirit #405C / CONCORDAT transport handoff

Native/MCP/service adapters must preserve domain qualification and cross-domain status rather than flattening foreign results to prose/boolean success.

For federated calls, transport should carry/preserve exact refs for:

source/target domain;
federation cut/frontiers;
federation/semantic/epistemic/PSC/RSC contract versions;
identity-mapping generation;
source trust-root/verifier ref and target appraisal result;
provenance/origin/dependence state;
losses/unknowns/noncomposable/resource-limited status.

Transport authentication of a foreign caller/result is not semantic warrant or host authority. No adapter may merge trust domains or infer local principal binding from semantic identity.

Canonical research: lost-rob0t/prolog-rlm#405C.

## Machine Spirit #405C / CONCORDAT transport handoff Native/MCP/service adapters must preserve domain qualification and cross-domain status rather than flattening foreign results to prose/boolean success. For federated calls, transport should carry/preserve exact refs for: - source/target domain; - federation cut/frontiers; - federation/semantic/epistemic/PSC/RSC contract versions; - identity-mapping generation; - source trust-root/verifier ref and target appraisal result; - provenance/origin/dependence state; - losses/unknowns/noncomposable/resource-limited status. Transport authentication of a foreign caller/result is not semantic warrant or host authority. No adapter may merge trust domains or infer local principal binding from semantic identity. Canonical research: lost-rob0t/prolog-rlm#405C.

nsaspy referenced this issue

2026-09-08 01:57:36 +00:00

[semantic-memory] Cross-memory entity/concept reconciliation, aliasing, ontology alignment, and reversible identity links #39

nsaspy referenced this issue

2026-09-08 01:57:39 +00:00

[EPIC][CORE] Library-first Symbolic Memory v1: durable semantic world model, learning history, federation, and zero-model recall #38

Rows
Columns

[semantic-memory] Expose general semantic ingestion, query, provenance, and bounded world-model projections through native/MCP tools #40

Goal

General tool surface

Knowledge coverage

Remember and symbolize stay distinct

Bounded projection

Source expansion

Prolog-RLM integration

Query result semantics

Authority/security

Acceptance

Machine Spirit #401C handoff — transport must preserve procedural admission/loss semantics

Upstream Machine Spirit #401D transport handoff

MACHINE-SPIRIT #402B handoff — transport status preservation

MACHINE-SPIRIT #402C handoff — native/MCP federation status preservation

Machine Spirit prolog-rlm#403A handoff — transport preserves projection risk/closure

Upstream Machine Spirit #403B transport handoff

MACHINE-SPIRIT prolog-rlm#403C handoff — transport must not flatten federation

Machine Spirit #403D transport handoff

MACHINE-SPIRIT #404A handoff — native/MCP learning status

Machine Spirit #404B / CITADEL-EPOCH native/MCP handoff

Machine Spirit #404C handoff — transport must preserve learning-transfer semantics

Implementation decomposition

MACHINE-SPIRIT #404D transport refinement

Machine Spirit #405C / CONCORDAT transport handoff