Name the asset, owner, and consequence
Define the code, data, site, app, account, file, or workflow; who owns truth; and which users, money, privacy, security, or production systems are affected.
Output: authority card
Short answer: start with the asset and consequence. Code changes belong in the developer route, test evidence in QA, warehouse changes in data operations, website/app choices in builder routes, and repeatable delegated work in agent/automation routes. No route grants silent access, deploy, data, spend, or public-action authority.
Tool choice comes after the workflowA code assistant, app builder, automation platform, or data tool is only useful after the owner, requirement, input, output, evidence, failure path, permission, and approval gate are clear.
Core technical occupation manuals
Manual 014 · Database operations
Database Administrators
Inventory estates, review access, separate backup from restore proof, plan migrations, diagnose performance, and prepare recovery evidence.
Open DBA manual →Manual 005 · Software engineeringSoftware Developers
Move from requirements to scoped implementation, mapped tests, review, release, rollback, and monitoring evidence.
Open developer manual →Manual 011 · Software qualitySoftware QA Analysts & Testers
Require reviewed test design, exact candidate identity, execution receipts, raw evidence, defects, traceability, and human release authority.
Open QA manual →Manual 013 · Data operationsData Warehousing Specialists
Trace source contracts, fields, transformations, validation, reconciliation, quality, cost, incidents, and warehouse change review.
Open data manual →Build a website or app
Website platform
AI Website Builder Tools
Choose based on ownership, editability, hosting, publishing control, and the workflow you actually need.
Compare builders →App platformAI App Builder Tools
Compare app-building routes by job, output, tradeoff, and handoff—not by demo spectacle.
Compare app builders →Website dataCookie Consent & Privacy Tools
Map consent, analytics, policy, and data-request workflows before adding trackers or claims.
Open privacy tools →Build agents and automations
Bounded agent
Agent Workflow Builder
Give AI one job card with approved inputs, least privilege, visible proof, and explicit human decisions.
Build an agent job →Workflow integrationWorkflow Automation Tools
Map triggers, actions, permissions, retries, failure states, and approval gates before connecting systems.
Plan an automation →Draft-first recipesAutomation Recipes
Browse practical automations that preserve review and stop before consequential actions.
Browse recipes →Protect the operating layer
Credentials and accountsUse a password manager, separate roles, least privilege, owner/expiry, and no secret copying into prompts.Password manager guide
Files and knowledgeDefine folders, permissions, retention, sharing, source-of-truth status, and what AI may index.Storage · Knowledge base
Project controlKeep requirements, owners, decisions, blockers, evidence, and change history visible.Project management
Cost and stack restraintAudit the actual workflow and leak before purchasing or connecting another platform.Run the stack audit
The shared technical route
Load the controlled baseline
Requirements, source contracts, designs, code/config versions, policies, standards, fixtures, approvals, and hashes.
Output: versioned baseline
Build one inspectable candidate
Use synthetic or approved inputs; bind tests and observations to exact candidate identity; retain raw evidence and limitations.
Output: evidence packet
Route the consequential action
Named humans retain credentials, access, spend, merge, deploy, data changes, production, rollback, publishing, and messages.
Output: approval_ready
Download the route map before adding another tool.
Use it to name the job, candidate, data boundary, proof, failure path, and exact human authority. Then open the specialist manual matching the real work.