@interf/compiler 0.7.0 → 0.7.1

package/README.md

@@ -2,16 +2,16 @@
 
 Interf prepares portable context for your agents.
 
-Agents now run real work from folders of PDFs, exports, notes, and transcripts. They don't reliably assemble the full picture from them: missed evidence, links lost across files, or answers that sound confident but are wrong. A chart inside one PDF can be obvious to a human analyst and easy for an agent to miss.
+Point an agent at a folder of files. It gets a partial picture. It picks up false hypotheses from a shallow read. Then it carries those into the work — missed evidence, links lost across files, confident answers that are wrong.
 
-The fix is structure: summarize the files, organize by category, link what belongs together. You tell Interf Compiler how — that's a compilation workflow.
+The fix is structure: summarize the files, organize by category, link what belongs together. You tell Interf Compiler how. That's a compilation workflow.
 
-`Interf Compiler` is the local runtime that runs compilation workflows on your files. Your local agent executes each stage. The compiler builds portable context — a local folder your agent reads. If the first build misses your questions, Interf improves the compilation workflow and builds again.
+`Interf Compiler` is a local runtime. It runs your compilation workflow on your files. Your local agent executes each stage. The output is portable context — a local folder your agent reads. If the first build misses your questions, Interf improves the workflow and builds again.
 
 ```text
 project-root/
   bristol-office-analysis/
-    report.pdf
+    report.md
     notes.md
     exports/
   interf.json                   # main config: works, source paths, questions, workflow choices, and defaults
@@ -28,7 +28,9 @@ The project root is the control plane. Your agent starts from `interf/<work>/` w
 
 ## What a Run Looks Like
 
-A recent public run — one PDF market report, two questions, two agents on the same setup — produced:
+Same files, same questions. What changes is whether the context was prepared first.
+
+A recent public run — one market report, two questions, two agents on the same setup — produced:
 
 <!-- PUBLIC_BENCHMARK_TABLE:START -->
 | Agent | Source files | Portable context |
@@ -45,9 +47,10 @@ The table is a sample, not a leaderboard. Run it on your own files. If you run m
 
 ## Design Choices
 
+- `Local-first`: your files, your questions, and your agent stay on your machine. No cloud, no uploads.
+- `File over app`: the portable context is a local folder next to the source files. Inspect it, diff it, version it.
 - `Check before build`: run `interf test --target raw` first — sometimes the source files already pass on your questions.
 - `Scored on your own questions`: every build is checked against questions you wrote from the files. If the portable context does not help, `interf test` tells you.
-- `File over app`: the portable context is a local folder next to the source files. Inspect it, diff it, version it.
 - `Bring your own AI`: use Claude Code, Codex, or another local agent.
 - `Explicit`: no hidden store, no hidden index. The portable context is plain files on disk.
 
@@ -110,8 +113,6 @@ interf/workflows/interf-default/
   improve/              # how Interf revises this compilation workflow if questions still fail
 ```
 
-Think of it as method -> output shape.
-
 - `workflow.json` describes the method: expected inputs, stages, and how the files should be processed.
 - `workflow.schema.json` describes the output contract: what files and folders the output must contain. Technically, this is the `context interface`, declared in `workflow.schema.json` and enforced by the compiler.
 - `compile/stages/<stage>/` is where you author one folder per stage — a small, specific phase like `summarize` or `structure`. You write the instructions; the compiler runs them with your local agent.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@interf/compiler",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Local, open-source context compiler for agent work. Build portable context from your files with a compilation workflow you define. Check on your own questions.",
   "type": "module",
   "bin": {