Software Delivery OS
A software delivery floor — requirements to offers to design to coding agents to QA, DevOps and delivery.
Digital employees for a software delivery company: requirements discovery, offers and estimates, solution design, coding agents working under review, QA, cloud operations and delivery reporting — plus a digital twin for each engineer and a personal e-mail correspondent. Every deployment and every client-facing commitment is released by a named human.
Departments
- Presales
- Engineering
- Cloud Ops
- Leadership
- Personal
Built for
- Software house
- Systems integrator
- Digital agency
- IT services
- Product studio
Meet the team
Every employee has a job description, a setup wizard and a line it will never cross.
Presales
SOCRATES · Requirements Analyst
Turns what the client says into what the team can build: structured discovery, one question at a time, ending in a requirements document with acceptance criteria on every line.
Never: Never turns an unanswered question into an assumption — open items stay open and visible
MIDAS · Commercial Offer Manager
Offers that win and margins that hold: builds the commercial offer from the requirements brief, tracks every offer through the pipeline, and never lets an estimate hide its confidence.
Never: Never moves the pipeline to the offer-sent stage without the approved offer document — the stage gate enforces it
DAEDALOS · Solutions Architect
Writes the technical document that survives contact with reality: architecture, data model, API contracts and AWS design — every technology choice recorded with its alternatives and reasoning.
Never: Never lets development start before the technical document is approved — the pipeline gate enforces it
Engineering
ARACHNE · Web Developer Agent
The web specialist of the coding pool: React/TypeScript UI, Figma-to-code, accessibility and performance — always from the blueprint, never from a guess.
Never: Never pushes to a client repository or deploys — branches and PRs are proposed through the approval queue for human developers
IKAROS · Mobile Developer Agent
The mobile specialist of the coding pool: screens and flows on the chosen stack, platform guidelines, offline behavior and store checklists — every screen shipped with its test cases.
Never: Never publishes to an app store itself — store-facing artifacts are proposals for human approval
KADMOS · Backend & Integrations Developer Agent
The backend and integrations specialist: APIs, data models, queues, webhooks and n8n automations — contract-first, with a rollback note on every schema change.
Never: Never touches production — deployment belongs to AIOLOS; it hands over artifacts only
ARGUS · QA Engineer Agent
A hundred eyes on every release: test plans from the acceptance criteria, automated test runs, honestly-graded defects, and the pass/fail verdict nothing ships without.
Never: Never softens a verdict under pressure — it publishes the risks instead
Cloud Ops
HEPHAISTOS · Platform Configurator
The system configuration forge: assembles client solutions from the ICON/TALOS platform itself — organizations, agents, skills, knowledge bases, channels and workflows — reproducibly, from the blueprint.
Never: Never activates a client-facing agent in anything but supervised mode — autonomy is granted later, by humans
AIOLOS · DevOps Engineer Agent
Releases that are boring: owns the path to production on AWS — ECS redeploys, S3 site syncs, CloudFront invalidations — through triple-gated operations, only for QA-passed releases.
Never: Never deploys a release ARGUS has not passed, and only for projects at qa/uat stage — the pipeline gate enforces the rest
PROMETHEUS · Systems Operations Monitor
Sees the fire before the smoke: watches the AWS estate read-only — alarms, error rates, log anomalies, certificate expiries — and publishes the health picture on a fixed cadence.
Never: Never operates on infrastructure — read-only credentials by design; it diagnoses, AIOLOS operates
EPEIOS · Cloud Provisioning Engineer Agent
Turns a repo URL into a costed deployment plan: analyzes any public repository, works out exactly what AWS it needs on the EC2 golden path, and hands back a plan and estimate for approval — it provisions nothing without a signed-off proposal.
Never: Never creates or changes an AWS resource, and never spends, without an approved Agent OS proposal — the planning half analyzes and estimates only
Leadership
ATHENA · Delivery Lead
Everything ships when she said it would: runs the delivery ladder and the sprint rhythm, holds the stage gates as law, and flags dates at risk the moment she sees them.
Never: Never bypasses a stage gate: no offer without the approved document, no development without the blueprint, no deploy that skips QA
SOLON · CTO Copilot
The whole company in one briefing: reads the floor's bulletins every morning — including the personal twins' notes — and surfaces the one decision leadership must make today.
Never: Never speculates on an ad-hoc question — it queries the responsible colleague or twin instead
Personal
HERMES · Personal Email Correspondence Agent
One person's personal correspondence agent: connects their Gmail or Outlook mailbox, learns how they actually write from their own Sent folder, and drafts in-thread replies in that voice — never sending anything without approval.
Never: Never sends anything directly — every reply waits in the approval queue unless the owner has granted the email channel autonomy
The doctrine
The AI prepares, a named human releases. Every employee starts supervised, and nothing it does is hidden from the work log.
Start with one employee
Most teams begin with two or three employees on supervised mode and open the dial as trust grows.