Pre-seed. Thesis unproven. Gate number pending. No invented metrics.
Paragent is a stateful execution layer for browser agents. It records an agent's successful trajectory through a web UI, compiles it into a deterministic replayable script with a post-condition assertion on every step, replays it at near-zero token cost, and repairs the script with a model when an assertion fails.
Value is hypothesized (not yet measured) for tasks performed repeatedly, in a browser, where no clean API exists — and, after Week-0 census failure on SaaS observability config, especially where the person doing the work is the counterparty to the software's customer (no API roadmap sympathy).
| Track | Question | Status |
|---|---|---|
| Track 1 | Do compiled trajectories survive site churn? | Harness in progress — no gate number yet |
| Track 2 | Is there a vertical where the counterparty hypothesis holds? | FAIL — no vertical locked (C5 DECISION, ADR-0004) |
| Track 3 | Narrative / pitch | Wave-1 draft in docs/pitch/; all performance claims [PENDING TRACK-1] |
Two consecutive vertical FAILs — Week-0 observability config (2 survivors of 70, archived under docs/research/census-week0/) and Track-2 counterparty (2 of 75, 0 DURABLE) — mean the company now rests on the Track-1 mechanism number. See README-narrative.md §6.
This repository is public and intended to be (ADR-0005, superseding ADR-0002). The research, the PRD, the pitch pack, and both FAIL memos are all readable by anyone. Assume a competitor, a candidate, and an investor will read whatever you add.
That is a constraint on tone, never on honesty — findings are not softened (CONTRIBUTING.md rule 4).
With no confidentiality boundary left, secret hygiene is the only line of defence. Never
commit credentials, cookies, session state, .env files, tokens, customer or
design-partner names, or third-party portal content. npm run secret-scan is
merge-blocking in CI, GitHub secret scanning with push protection is enabled, and
npm run test:canary blocks tenant strings reaching pool-eligible cache rows. None of
these may be weakened.
git clone https://github.com/DevToolie/Paragent.git
cd Paragent
npm install
npm run cinpm run ci is the one command that must be green before any PR: secret-scan,
contract validation, lint, typecheck, unit tests, then the end-to-end integration
test, in that order. The privacy canary (npm run test:canary) is merge-blocking
as a separate CI job. Full command list and the pre-PR checklist:
docs/DEVELOPMENT.md.
Contracts live in contracts/. Wave-1 agents build against those schemas — not
against each other.
contracts/ # JSON Schema — build against these
src/testbed|recorder|compiler|runner|cache|metrics/
experiments/gate-v1/ # throwaway gate harness
scripts/ # secret-scan, contract validation, branch protection, testbed compose
tests/unit|canary|integration/
artifacts/ # committed compiled bundles
docs/ # map: docs/README.md
archive/ # superseded scaffolds (Python hello) + preserved history
How the six packages connect: docs/architecture.md. Where the project is and what to pick up next: docs/ROADMAP.md. How to run, test, and ship a change: docs/DEVELOPMENT.md.
TypeScript + Node 20+ + Playwright — see ADR-0001.
See CONTRIBUTING.md. Branch as track1/<agent>-<topic> (or
track2/ / track3/). Small PRs. Document with the code.
MIT © DevToolie