Thalo boundary

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

Boundary and evidence

This run analyses Thalo as a structured plain-text knowledge system for human and AI collaboration, not merely its parser API. Intended use is to characterize how retained entries are produced, checked, queried, selected for synthesis, rewritten and consumed on later passes. The target class is memory/knowledge/context-engineering system; the boundary kind is whole-system. The README declares this knowledge use and distinguishes context preparation from downstream model generation (SRC-1, README.md):

Thalo is a plain-text format that gives your knowledge just enough structure for tools and AI to work with it, while staying readable and editable by humans. Just text files in git, editable in Cursor or by Claude Code. --- README.md

Actualization is intentionally minimal. It runs the user-defined query and prints the new entries that match the query together with the prompt. This can then be piped to an LLM to do anything, but generally to create synthesized content. --- README.md

The functional boundary includes the language, parser, workspace and schema model, checker, queries, Git and timestamp change tracking, CLI, formatter, merge driver, editor integrations, browser playground, authored instructions and example KB. It also includes the GitHub synthesis action and the shipped Pi synthesis command. These are not excluded enclosing applications: the repository supplies both their state-handling code and a workflow connecting them. The root CLI registers initialization, checking, querying, actualization, formatting, language-server and merge commands (SRC-1, apps/thalo-cli/src/mod.ts). The CLI loads .thalo and Markdown files into a workspace, while actualization reloads synthesis definitions and their latest checkpoint entries (SRC-1, apps/thalo-cli/src/files.ts, packages/thalo/src/services/synthesis.ts, packages/thalo/src/commands/actualize.ts).

The action passes selected entries and checkpoints to a command, then commits and pushes resulting file changes and creates or updates a pull request. The shipped workflow selects the repository's Pi command and the thalo-test KB. This establishes an inspectable model-dependent path within the target, despite the CLI's deterministic context preparation (SRC-1, packages/thalo-action/src/action.ts, .github/workflows/test-action.yml):

  - name: Test action
    uses: ./packages/thalo-action
    with:
      github-token: ${{ secrets.GITHUB_TOKEN }}
      command: node ../packages/scripts/src/synthesize-with-pi.mjs
      syntheses: ^typescript-guide
      working-directory: thalo-test

--- .github/workflows/test-action.yml

The command reads existing synthesis-file content, combines it with the selected entries and prompt, calls a Pi agent and writes updated Markdown plus an actualization checkpoint. Subsequent workspace loading and latest-actualization lookup are included, not just the returning prompt API (SRC-1, packages/scripts/src/synthesize-with-pi.mjs, packages/thalo/src/services/synthesis.ts):

await agent.prompt(userPrompt); --- packages/scripts/src/synthesize-with-pi.mjs

await writeFile(absoluteFilePath, updated); --- packages/scripts/src/synthesize-with-pi.mjs

External dependencies include Node.js, Tree-sitter/native or WASM parser support, the filesystem and Git, the VSCode/LSP host, GitHub Actions and its API, and the Pi packages and OpenAI service used by the shipped command. Their implementations, provider behavior, credentials, deployed services and human PR approval are outside the frozen repository. These exclusions prevent conclusions about provider reliability, enclosing-agent planning, production hosting and actual human acceptance. They do not exclude Thalo's adapters, prompts or Git publication code. A caller-supplied synthesis command is an external extension point; only the shipped command's implementation is frozen (SRC-1, packages/thalo-action/action.yml, packages/thalo-action/src/action.ts, packages/scripts/src/synthesize-with-pi.mjs, packages/thalo-vscode/src/mod.ts).

The acquired checkout is frozen at cdb9aae983e6bc0b75eff1606bc99b088c3aebff; HEAD matched this pin and the checkout was clean when inspected. The analysis cutoff is 2026-10-14, the supplied run date, not a claim that the source reflects later development. Overall evidence is code-grounded: implementation and source-native doctrine are available. No target execution, tests, provider requests or service calls were performed. Test source and a configured workflow are not observed successful operation; they cannot establish synthesis quality, operational reliability or causal improvement.

Repository coverage

Every tracked top-level file or directory is classified below. Included scope is the run's coverage obligation, not a claim that every file has already been read. All listed implementation paths remain eligible for later inspection at the same commit. No material shipped loop path was unavailable. Items marked not yet inspected are available evidence, not access gaps.

Coverage anchors are SRC-1, README.md, CLAUDE.md, package.json, apps/thalo-cli/src/mod.ts, apps/thalo-cli/src/commands/init.ts, apps/thalo-cli/src/commands/check.ts, apps/thalo-cli/src/commands/merge-driver.ts, apps/docs/app/components/playground/thalo-runner.ts, packages/thalo/src/vfs/persistence.ts, packages/thalo-lsp/src/server.ts, packages/thalo-vscode/src/mod.ts, packages/thalo-prettier/src/mod.ts, skills/thalo/SKILL.md, thalo-test/AGENTS.md and specs/README.md. Tracked-path inventory supplies placement, not behavioral claims for uninspected files.

Source register