Text Brief
Turn supplied source material into a faithful, reviewable brief—with fully local inference.
The product layer for agent workflows
Bring the workflow that already works in Pi, Hermes, OpenClaw, or your own stack. The factory adds a focused interface, pinned tools, an isolated runtime, managed inference, narrow permissions, evaluations, signing, and updates.
12 KBMap the source18 claims · 6 supporting passages
DoneResolve contradictions2 tensions retained as open questions
DoneValidate the claimsChecking every section against source text
RunningBuild the briefSummary · evidence · decisions · gaps
NextApps, not agent demos
The strongest candidates are narrow, repeatable jobs with a clear start, governed actions, and a finished result. Two apps already exercise the shared factory; four show where it can go next.
Turn supplied source material into a faithful, reviewable brief—with fully local inference.
Inventory only selected files with names, sizes, and checksums—without packaging a model.
research.pdf2.8 MB
7f3a…91b2notes.md18 KB
01c9…44a1claims.csv42 KB
a923…e101Turn a bounded set of sources into a decision-ready dossier with evidence, disagreements, and open gaps intact.
Match receipts against a ledger, surface missing evidence, and propose reviewable changes—without posting them.
OpenAIReceipt matched · $200.00
ReadyFigmaPayment found · receipt missing
ReviewUnknown chargeNeeds owner classification
AskInspect a packaged build, run declared smoke tests, and produce a release decision with exact evidence.
ARTIFACTRelease.appv1.4.0-rc2
Apply a house style across a batch of drafts, explain each edit, and leave the final decision to the author.
We leverage a comprehensive solution to enable…
Use one focused workflow to turn the source into…
Built now means the app exercises the current shared factory. Designed for is an example of the product shape, not a shipping claim.
The market gap is capability delivery
A technical user can often reproduce the underlying behavior. The hard part is making it dependable, legible, governed, and distributable to everyone else.
$ git clone workflow$ brew install python node llama.cpp$ export PROVIDER_KEY=••••••$ agent --skills ./skills --tools allError: model server unavailableAGENT APPLICATIONText Brief.appSigned · self-contained · updateable
A reusable application compiler
A new product should mostly require a portable skill, manifest, interface schema, deterministic tools, fixtures, and branding—not a new runtime, policy system, updater, or release pipeline.
01APPLICATION SOURCE
Portable skillReasoning, sequencing, validation, escalation
Workflow + UI schemaInputs, plans, approvals, results, exports
Deterministic toolsRegistered scripts, APIs, storage, OS actions
Capability policyMaximum files, domains, secrets, and actions
Evaluation casesRepresentative, adversarial, cancellation, cleanup
02SHARED FACTORY
03FINISHED ARTIFACT
One install. One job. Explicit authority.
Intended toolchain
Each command makes a different promise explicit: valid authority, measured behavior, reproducible packaging, exact-artifact smoke tests, and a governed release.
➜skillapp validate text-brief
✓ manifest schema
✓ registered tools
✓ capability policy
✓ offline contract
VALID · 0 unsupported capabilities
Task-specific product experience
The interface carries the workflow: structured input, a reviewable plan, bounded approvals, visible progress, safe cancellation, and an inspectable result.
The user supplies the source, purpose, and constraints through fields the app can validate before any model runs.
Add the source and tell the app what the brief must preserve.
The app translates the skill into visible, cancellable steps.
Map the sourceExtract claims, evidence, decisions, and unresolved questions.
≈ 35 secResolve contradictionsRetain tensions rather than inventing a single answer.
≈ 20 secValidate every sectionTrace the brief back to supplied source passages.
≈ 55 secRender and exportWrite only to the chosen location.
ApprovalAuthority for this runRead supplied text · bundled tools · no network · ask before export
Checking every section against source text.
Source map complete18 claims · 6 evidence clusters · 2 tensions
09:42:11Contradictions retainedNo unsupported reconciliation introduced
09:42:29Validating section 4 of 6Checking “managed inference” against source passages
RunningRender final briefWaiting for validation pass
QueuedOffline enforced0 network requests · 1 owned process
Every section remains traceable to the source.
DECISION BRIEFAgent App Factory
Source coverage 96%Prove that several materially different applications can share one dependable runtime and packaging system before expanding the capability surface.
CORE INSIGHTSkills make expertise executable. The factory makes that expertise installable.
Two applications already test both agentic and deterministic paths.
Public signing, notarization, update apply, and rollback remain release gates.
The task is encoded in the product—not hidden in a prompt.
Pause, cancel, recover, and clean up are first-class behavior.
Narrow authority by construction
Every agent action crosses a deny-by-default broker. Capabilities are scoped to one finite run, consequential actions can require one-action approval, and access is revoked when the job ends.
Deny by defaultUnsupported capabilities fail validation instead of receiving broad access.
Selected resources onlyFiles and export locations come from explicit user choice.
Approval at consequenceThe app can plan freely while exact writes and external actions stay gated.
Authority expiresRun-scoped capabilities and owned processes are revoked and cleaned up.
Current proof
The claim only matters if agentic and deterministic products can share the shell, policy, lifecycle, diagnostics, and packaging system without forcing every task through an LLM.
AGENTIC APPLICATIONText Brief
LOCAL MODELA real semantic workflow through Pi Agent Core, a private bundled llama.cpp runtime, and Qwen3-4B—with no account, API key, subscription, or hosted fallback.
DETERMINISTIC APPLICATIONFile Inventory
NO MODELA focused utility that inventories explicitly selected files with names, sizes, and checksums while packaging no model and no agent runtime.
Structured output, tool behavior, cancellation, and semantic quality all passed across the 30-run benchmark.
Current prototype: evidence for the architecture, not a claim that public distribution is complete.
Who the factory is for
You already have a skill or agent workflow that works. Ship it without rebuilding model management, policy, UI, packaging, evaluation, and updates.
Your method combines judgment with repeatable machinery. Turn that expertise into a focused product instead of a prompt library or consulting-only workflow.
You need reproducible behavior, declared authority, review points, and evidence—not a general agent with ambient access to company systems.
Build the workflow once
Prove the shared factorySeveral useful Mac apps · local and deterministic paths · dependable runtime
Expand explicit execution modesExisting AI subscriptions · paid APIs · more local models
Add new product primitivesScheduling · event triggers · supervised computer use · catalog distribution
Early access
Tell us what you have built—or what finished agent app you wish existed. The earliest design partners will shape the first reusable application contracts.