@meta v: 1 route: / generated: 2026-10-04T22:22:21Z ttl: 1d @intent purpose: Explain how KrakenOS lets one person direct and supervise a private digital workforce audience: visitor, prospective-client, ai-agent capability: learn, evaluate, contact, sign-in @state product: KrakenOS company: Titanium Computing headline: A digital workforce with its own managers. One person at the top. summary: "KrakenOS gives every project its own lead and its own team of AI workers, all run by one lead that acts as project manager. They work through the night. Anything that needs a person comes up the chain to one list on my phone. That person is me." operating_model: owner_contacts: one lead lead_role: acts as project manager and manages project leads worker_reporting: workers report to their lead, never directly to the owner supervision_interval: every 30 minutes morning_summary_deadline: before 8:30 every morning routine_decision_default: after one hour without an owner answer always_waits[6]: Deleting data, A public launch, A major version, Posting under my name somewhere new, Breaking something people use, Anything customer-facing that's hard to undo phone_supervision: input: jobs given by chat queue: approvals, decisions, owner-only sign-ins, blockers item_detail: reason and recommended answer response_flow: owner answer goes to the lead for action sample_morning_summary: label: Sample text: "Shipped: the onboarding guide and a second pass on the price sheet. Stuck: a site update waiting on a sign-in only I can do. Needs me: two decisions. Top three today: the sign-in, the launch date, the next draft." sample_phone_decision: label: Sample question: When does the new pricing page go live? reason: "The page is finished and checked. Going live is public, so this waits for me." recommendation: Tuesday morning. privacy: customer_data: never leaves company-owned hardware builds_and_tests: run on company-owned hardware wherever possible credentials: stored in a vault and referred to by name only, never pasted into chat or code owner_rules: override defaults sections[6]{title,summary}: I talk to one lead,"KrakenOS is organised like a small company. One lead acts as my project manager. Each project has its own lead, and each project lead runs its own team. Workers report up that chain and never message me directly, so the only conversation I keep up with is the one with the lead." How this page got made,"I asked for a page about KrakenOS. A team wrote four directions, checked every claim against a written list of facts, and held them until I picked one. Anything customers will see starts that way. Along the way the leads pick the AI model that suits each job, write decisions down as they land, and shut workers down once they're finished." It keeps working after I go to bed,"Every 30 minutes a check looks for any lead that has gone quiet, nudges it, and escalates if it stalls again. It never shuts anything down. Before 8:30 there's one summary waiting, on a schedule, so nobody has to remember to send it:" Everything that needs me is on one list,"I give it jobs by chat from my phone. When the team needs me, it goes on one list the moment it comes up: an approval, a decision, a sign-in, or something blocked. Each item says why it's there and what the team recommends. My answer goes straight back to the lead, which acts on it." What happens when I don't answer,"Most items carry a default. After an hour without an answer, the team takes its recommendation, notes on the item that it did, and keeps going. A short list never moves without me: deleting data, a public launch, a major version, posting under my name somewhere new, breaking something people use, and anything customer-facing that's hard to undo. If I want different defaults, I change them on my rules page. What I set there wins." Customer data stays on our hardware,"Customer data never leaves our own machines, and builds and tests run on them wherever they can. Passwords live in a vault. Agents refer to a credential by name and never paste the value into chat or code." proof_points[6]{title,fact}: "Options first, then a decision","Four directions, every claim checked against a list of sources, nothing built until I picked." One summary before 8:30,"What shipped, what's stuck, what needs me, and the top three, sent on a schedule." Stalled work gets a nudge,A check nudges a stalled lead and never stops a process. A reason and recommendation,Anything that needs me arrives with a reason and a recommended answer. Workers report to their lead,"I talk to the lead, never to each worker." Data and credentials stay protected,Customer data stays on company hardware. Credentials are reported by name only. contact: sales: https://titaniumcomputing.com/contact/ support: mailto:support@titaniumcomputing.com support_hours: Monday to Friday, 9 AM to 5 PM Central agent_support: /support/agent.md @actions - id: talk_to_titanium_computing method: GET href: https://titaniumcomputing.com/contact/ description: Talk to Titanium Computing about what a team like this could take on. - id: sign_in method: GET href: https://desk.semfreak.dev/login description: Sign in to KrakenOS - id: contact_support method: GET href: mailto:support@titaniumcomputing.com description: Email customer support - id: read_agent_support method: GET href: /support/agent.md description: Diagnose and draft a support request @context > A digital workforce with its own managers. One person at the top. > KrakenOS gives every project its own lead and its own team of AI workers, all run by one lead that acts as project manager. They work through the night. Anything that needs a person comes up the chain to one list on my phone. That person is me. > KrakenOS is a product by Titanium Computing. Sales conversations start on the Titanium Computing contact page. @nav self: /.agent parents: [] children: [/support.agent] peers: [/support.agent]