A.M.O.S.
ShippedTri-daemon prompt watchdog. Three scoring heads evaluate every candidate action; any head can halt, none can authorize alone. CLI, HTTP API, plugin system, versioned rollback.
ADHDAKOTA // Independent systems engineering
Operating systemsfor the self
Identity engines, workflow modules, and agent personalities — built for neurodivergent minds, founders, and creators who need a system that runs the way they do. Fixed scope, fixed price, written spec before any money moves.
Written spec first · Source delivered to your repo · 14-day fix window
modules0
agents0
surface—
runtime—
tierunconfigured
build time—
The lab
Run the systems
Four live engines. Configure a build, arbitrate an action, scan a config for leaked credentials, score a project for release. Every one runs on this page — no accounts, no uploads, no calls out.
Module rack loads with the page script.
Candidate action
- neg_worst
- —
- floor_tripped
- —
- authorization
- any head may halt; none may authorize alone
Paste a config, env file, or log
Readiness checks
Agent
idle
Definitions
What the words mean
Every tier is priced in these units. Nothing is listed below that isn't defined here.
- Workflow module
- One automation that runs end to end without you: a scheduled script, webhook handler, sync job, or CLI command. Delivered as source, documented, with a rollback path.
- Agent personality
- A configured AI assistant with a fixed system prompt, tool access, and guardrails, pointed at your data. Runs on your API key or locally through Ollama.
- Identity engine
- The shell tying modules together: a command surface, shared config, logging, and a start/stop routine so the whole system survives a reboot.
Prior work
Systems already built
Status is labeled straight. Shipped means running. Prototype means the core works and the edges don't.
NOMX
ShippedLocal command center. Python and SQLite engine that scores project readiness before release, running entirely on-device under Termux.
Pinky Hub
PrototypeLocal AI hub: Flask UI over llama.cpp with hot model swapping, plugin manifest parsing, and multi-model fusion modes. Runs offline.
nuke_scanner
ShippedFilesystem secret scanner and cleanup tool for Android. Finds credentials left in project directories and quarantines them before they reach a repo.
FMOne
PrototypeOne-shot installer and daemon that reads a capability baseline, generates the missing service stubs, and pushes each to its own repo.
Cold Fusion AI
PrototypeChat OS built on its own stack. Listing on There's An AI For That; the engine is the product, not a wrapper on someone else's endpoint.
Digital Aether
ShippedSingle-file ecosystem hub cataloguing twelve web apps, live status, and a link audit — the index that keeps a large personal system navigable.
Distribution
Three tiers. One spec each.
Half up front, half on delivery. Nothing is billed until you approve a written scope, so the price you see is the price you pay.
Tier 1
Starter OS
$149Fixed · one build
- Includes
- 2 workflow modules, 1 agent personality
- Surface
- CLI or single-page dashboard
- Delivery
- Source in your repo + setup doc
- Turnaround
- 7 days from approved scope
- Support
- 14 days of fixes
Not included: hosting, third-party API costs, ongoing maintenance.
Tier 2 · Most requested
Life OS
$449Fixed · one build
- Includes
- 5 workflow modules, 2 agent personalities, identity engine
- Surface
- Dashboard with logging and start/stop control
- Delivery
- Source in your repo + setup doc + walkthrough call
- Turnaround
- 14 days from approved scope
- Support
- 30 days of fixes
Not included: hosting, third-party API costs, ongoing maintenance.
Tier 3
Professional OS
From $1,200Quoted after scope call
- Includes
- 10+ modules, 4 agent personalities, identity engine, integrations
- Surface
- Dashboard, API, deployment to your server
- Delivery
- Source, runbook, handover session
- Turnaround
- 3–5 weeks, staged milestones
- Support
- 60 days of fixes, retainer optional
Not included: hosting, third-party API costs, compliance certification.
Something else? Hardware interfacing, OBD-II and embedded work, or a system that fits no tier. Describe it and you get a fixed quote or a straight no.
Describe the projectHow a build runs
Four steps, in this order
The sequence is the product: nothing is built before the spec is signed, nothing is billed before you've seen what you're buying.
Intake
You describe the problem in writing or on a 20-minute call. No charge, no obligation.
Scope document
You get a written spec: every module named, its inputs and outputs, the delivery format, the fixed price. You approve it or you walk.
Build
Work runs against the spec. Commits land in your own repo as they happen — no surprise at the end.
Handover
Setup doc, walkthrough, and the fix window opens. Anything in the spec that doesn't work gets fixed at no cost.
Answers
Before you send money
What do I own at the end?
All source, in a repository you control, licensed so you can modify and run it without me. No per-seat fees, no phone-home.
What if it doesn't work?
Anything in the approved scope that doesn't work gets fixed inside the support window at no charge. If a build can't be made to meet its own spec, the balance is refunded.
Refunds?
Full refund of the deposit any time before build work starts. After that, refunds cover the unbuilt portion of the scope.
What happens to my data?
Only what you send to get the work done. It sits on encrypted storage, isn't sold or shared, and is deleted on request within 30 days. Builds run on your infrastructure and your API keys, not mine.
Does this site track me?
No third-party analytics, no ad pixels, no cross-site tracking. Settings you choose here are stored on this device only.
Who's behind it?
Dakota Moses, working as ADHDAKOTA. Self-taught systems engineer; background across software, hardware, and automation. Prior builds are listed above and the code is public where it can be.
Intake
Describe the problem
What you write here becomes the first draft of the scope document. Specifics beat pitches.
Replies within one business day.