Antinomia boundary

Type: agentic-system-analyses/types/agentic-system-boundary.md

Boundary and evidence

Antinomia is in scope as a memory/knowledge/context-engineering system: an Obsidian plugin that retains typed notes and uses model calls to classify input, extract material, propose transformations and identify contradictions. Its intended use is reflective personal knowledge work, not an autonomous enclosing agent runtime. The source calls this Personal Tension Management and cautions against treating Hunter proposals as decision-support truths (SRC-1, README.md).

Antinomia is an Obsidian plugin for Personal Tension Management (PTM) — the in-tension counterpart of Personal Knowledge Management. --- README.md

The whole-system boundary is the shipped plugin, including its interactive drivers, prompts, admission interfaces, note persistence, maintenance, subsequent note consumers and evaluation material. It is not merely the AI transport library. The build enters through main.ts; its plugin class loads settings, registers views and commands, and exposes creation and modification operations. Shipped views, modals and helpers are internal callers, not excluded host applications (SRC-1, esbuild.config.mjs, main.ts).

The initial trace follows the loop across these responsibilities:

• Produce and admit: command registration in main.ts reaches free input, guided note creation, PDF/YouTube ingestion, elevation and presupposition mapping. Search traced model calls and note writes in all shipped flow files. The presupposition confirmation modal collects new/link/skip decisions before applyPresuppositionDecisions creates notes and updates both directions of retained links (SRC-1, main.ts, flows/freeInput.ts, flows/pdfIngest.ts, flows/youtubeFetch.ts, modals/PresuppositionMapModal.ts, flows/presuppositionMap.ts).
• Persist and maintain: createNote writes Markdown through the vault API; settings use plugin loadData/saveData. Elevation, resolution, defeated archiving, link maintenance, schema migration/backup/restore and presupposition delete synchronization belong to the target (SRC-1, main.ts, flows/elevation.ts, flows/migration.ts, flows/presuppositionMap.ts).
• Reload and consume: the frontmatter helper reads Obsidian's metadata cache. Hunter reads retained Markdown bodies and typed metadata, selects open tensions and substrates, constructs a bounded prompt and calls the configured backend. Previously dismissed pairs are read from note frontmatter and filtered from later results. Graph, list, dashboard, audit and dependency-map views are additional shipped consumers (SRC-1, core/frontmatter.ts, flows/hunter.ts, views/AntinomiaGraphView.ts, views/DashboardView.ts, views/AuditVaultView.ts, views/PresuppositionsMapView.ts).
• Evaluate: the example-vault flow writes seeded contradictions, noise and a human-readable Hunter measurement key. Tests cover parsers, model detection, frontmatter and selected maintenance flows, including mock-vault presupposition integration. These are evaluation designs and assertions, not evidence that a live run passed (SRC-1, flows/exampleVault.ts, tests/README.md, tests/flows/presuppositionMap-integration.test.ts).

Minimum implementation passages supporting the retained-state loop:

const file = await this.app.vault.create(path, content); --- main.ts

return app.metadataCache.getFileCache(file)?.frontmatter; --- core/frontmatter.ts

const isOpenTension = t === TYPE.tension && fm?.status === "open"; const isSubstrate = t === TYPE.substrate; if (isOpenTension || isSubstrate) candidates.push(f); --- flows/hunter.ts

fm.presupposes = toWikilinks(mergeUnique(prev, uBasenames), titleMap); --- flows/presuppositionMap.ts

The frozen evidence is SRC-1 at commit 6fafd01082fbecb2a18803500a1abe70a2bdc9f4, with applicability cutoff 2026-11-08. HEAD was checked against the acquired pin. The overall tier is code-grounded, supplemented by the repository's own doctrine/design. No target code, tests, examples or model requests were executed.

Tracked top-level coverage

“Included” means within the functional evidence boundary; the inspection column distinguishes initial tracing from material available for later detailed inspection. No material shipped state-loop path is deliberately excluded.

External dependencies and excluded evidence

Obsidian's vault, metadata cache, workspace and plugin storage APIs are external runtime dependencies. The plugin's calls to them are included; Obsidian implementation and a real user vault are not frozen. This prevents conclusions about host atomicity, cache timing guarantees, synchronization durability or actual user outcomes. main.ts and core/frontmatter.ts establish the dependency, not those guarantees (SRC-1).

Configured Anthropic/OpenAI-compatible model services, local servers and their model weights are outside the frozen source. ai/callAI.ts implements request routing; it does not freeze providers or establish model accuracy, privacy enforcement or operational availability. YouTube/transcript services and PDF host facilities are dependencies reached by the shipped ingest flows, not additional evidence sources (SRC-1, ai/callAI.ts, flows/youtubeFetch.ts, flows/pdfIngest.ts).

Installed dependency implementations, built release binaries, live Obsidian desktop/mobile behavior and actual model execution traces are not supplied as frozen run evidence. This prevents claims of successful installation, end-to-end correctness, measured contradiction-detection quality or causal improvement. Repository tests and response fixtures remain inspectable source material; their existence does not remove these limits. Linked external papers, newsletters, provider documentation and release pages are not registered sources and were not followed. This prevents treating their contents as evidence for this run. Available-but-uninspected repository files in the coverage table are not access gaps and remain eligible for later inspection at this same pin.

Source register