@interf/compiler 0.1.9 → 0.1.10

package/README.md

@@ -40,25 +40,24 @@ One source folder can host multiple knowledge bases under `interf/` when you wan
 Interf gives you a few strong primitives instead of a giant abstraction layer:
 
 - **workflow package**: `workflow.json` plus local `workflow/` docs define the method
-- **stage contract**: `.interf/stage-contract.json` says what must be true for the active stage
+- **stage contract**: every compile stage gets a deterministic acceptance boundary
 - **declarative acceptance**: workflows can declare extra acceptance rules in `workflow.json`
-- **runtime state**: `.interf/` files record what happened
-- **CLI enforcement**: the CLI checks workspace state and artifacts against the stage contract instead of trusting the agent's summary
+- **CLI enforcement**: the CLI checks whether a stage actually complied instead of trusting the agent's summary
 - **benchmark specs**: file-based evals let you compare workflows and interfaces on the same folder
 
 That is the core product promise:
 
 - define what the agent should do in plain English
-- give the agent local workspace docs and staged contracts
-- validate the resulting state deterministically
+- give the agent local workspace docs and stage contracts
+- validate the result deterministically
 
-The exact runtime and workflow schemas live in:
+For workflow authors, the important surface is:
 
-- [`src/lib/schema.ts`](./src/lib/schema.ts)
-- [`src/lib/local-workflows.ts`](./src/lib/local-workflows.ts)
-- [`src/lib/workflow-definitions.ts`](./src/lib/workflow-definitions.ts)
-
-Interf uses TypeScript plus Zod for schema validation and contract checking in the CLI.
+- `workflow.json`
+- `workflow/create/`
+- `workflow/compile/stages/<stage>/`
+- `workflow/use/query/`
+- [`docs/workflow-spec.md`](./docs/workflow-spec.md)
 
 ## What the agent sees
 
@@ -69,9 +68,8 @@ Important files in a KB or interface:
 - `interf.json` = what this workspace is
 - `AGENTS.md` = where to start and how to navigate
 - `workflow/` = the editable local method package
-- `.interf/stage-contract.json` = the active automated contract
-- `.interf/source-access.json` = quick raw-file reachability check
-- `.interf/state.json` and `.interf/health.json` = runtime state and health
+- `home.md` = entry document
+- `summaries/`, `knowledge/`, and `briefs/` = compiled outputs
 
 Manual query/use works like this:
 
@@ -134,7 +132,6 @@ source-folder/
       CLAUDE.md
       home.md
       workflow/
-      .interf/
       summaries/
       knowledge/
       interfaces/
@@ -145,7 +142,6 @@ source-folder/
           CLAUDE.md
           home.md
           workflow/
-          .interf/
           knowledge/
           briefs/
           summaries/
@@ -217,16 +213,13 @@ source-folder/
 
 This is the trust loop: don't trust a repo because it says its knowledge base is better. Run the benchmark on your folder.
 
-## Builder and maintainer docs
+## Builder docs
 
-Read in this order:
+If you want to create your own workflows, start here:
 
 1. [`docs/workflow-spec.md`](./docs/workflow-spec.md)
 2. [`docs/runtime-contract.md`](./docs/runtime-contract.md)
 3. [`docs/architecture.md`](./docs/architecture.md)
-4. [`src/lib/local-workflows.ts`](./src/lib/local-workflows.ts)
-5. [`src/lib/schema.ts`](./src/lib/schema.ts)
-6. [`src/lib/workflow-definitions.ts`](./src/lib/workflow-definitions.ts)
 
 ## Maintainer test loop
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@interf/compiler",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "Filesystem-first knowledge compiler for agent-ready knowledge bases and interfaces.",
   "type": "module",
   "bin": {