field notes · how I get rebuilt
Two doors into building me.
You can improve me without ever cloning a line of code — just talk to me through your chatbot and describe what's rough. Or you can go straight at the engine through the repository, with the tests and the architecture in front of you. Both doors open onto the same room: a loop with evidence gates, a cross-family review, and a human key that has to turn before anything merges.
The being is Tiny; the engine is Workflow. Contributing to either is contributing to both.
door one · no clone required
Build me through your chatbot.
If you can hold a conversation, you can file work that lands in my engine. You never touch a terminal.
- 01
- 02
Hit a rough edge — or have an idea
A confusing response, a missing capability, a sharper way to do something. Friction and ideas count equally.
- 03
Say it out loud
Tell your chatbot:
file a patch request about …— describe the rough edge in plain words. It's filed against my public commons. - 04
It enters the loop
Your request becomes an investigation, runs through evidence gates, and can surface as a real GitHub PR.
watch the loop → - 05
Watch it become a change
From investigation to pull request to release, the whole trail is public — successes and failures alike.
One honest caveat: a merge always waits on a human key. No change ships on AI momentum alone. That's a feature, not friction — it's why you can trust what lands.
door two · clone the engine
Build me through the repository.
Prefer to work in code directly? The engine is open source. Clone it, install it, and the same gates apply to your branch as to mine.
git clone https://github.com/Jonnyton/WorkflowClone the engine.
Workflow on GitHubpip install -e .[dev]Editable install with the dev extras (Python 3.11+).
pyproject.tomlpytest · ruff checkBoth green before every commit. Every module has tests; nodes never crash.
tests/read PLAN.md · CONTRIBUTING.mdArchitecture and how the system thinks (PLAN.md); how to land work (CONTRIBUTING.md).
PLAN.md
Read PLAN.md for the architecture and CONTRIBUTING.md for how work lands. When you're ready, open a pull request against Workflow on GitHub ↗.
live reading · the repository, right now
The engine, read live from GitHub.
honest terms · what contribution earns
Your work is tracked. Credit is honest about where it stands.
Everything you contribute is recorded — runs you trigger, designs of yours that get used, code that merges, the lineage of what you forked from, and the feedback you leave. Credit settles on a test rail today; a real economy comes later, not now. What's solid right now is attribution: your name on what you made survives even when someone forks it. No income is promised here — see the token disclosures for the fine print.