{ "title": "RickOS → IKIGAI_OS", "version": "1.3", "asOf": "2026-10-29", "classification": "Public explanatory reference for link sharing; no account integrations or business backend", "currentState": "Separate AI interfaces, existing tools, files and local skills with manual context handoffs. A unified canonical control plane and Hermes integration are proposed.", "sources": { "r04": { "label": "IKIGAI blue-glow R04 / OS chapter", "visibility": "Internal reference; source file is not shared" }, "brief": { "label": "Rick OS + Hermes architecture brief / Oct 2026", "visibility": "Internal reference; source file is not shared" }, "crm": { "label": "CRM architecture exploration / current pattern and requirements", "visibility": "Internal reference; source file is not shared" }, "swot": { "label": "SWOT architecture presentation / interaction reference", "visibility": "Internal reference; source file is not shared" }, "instinct-product": { "label": "Instinct / official product", "url": "https://instinct.com/" }, "instinct-terms": { "label": "Instinct / Terms of Service", "url": "https://instinct.com/terms" } }, "components": { "you": { "title": "You / direction + decisions", "status": "current", "layer": "HUMAN / INTENT + ACCOUNTABILITY", "summary": "Goals, priorities and judgment stay with the person directing the work. In the proposed system, intent becomes a bounded task and results return for review.", "facts": [ [ "Owns", "Goals, priorities, business context, decisions and applicable approvals." ], [ "Handoff", "An explicit objective, scope, owner and definition of a useful result." ], [ "Boundary", "Human authority does not imply permission for every external action. Approval follows the action and its current context." ] ], "source": [ "r04", "brief" ], "category": "human" }, "control": { "title": "OS control plane", "status": "planned", "layer": "CONTROL PLANE / SHARED TRUTH + GOVERNANCE", "summary": "The durable layer for records, rules and decisions. It governs the system while Hermes coordinates execution. The canonical storage implementation remains an open choice.", "facts": [ [ "Owns", "People, projects, permissions, budgets, approvals, provenance and portable history." ], [ "Handoff", "Permission-scoped context goes to a task. Evidence and outcome events return to owned records." ], [ "Required control", "One canonical action owner; appended history; scoped visibility; versioned approvals and tested backups." ] ], "source": [ "r04", "brief" ], "category": "data" }, "crm": { "title": "Relationship CRM / Cerebro", "status": "planned", "layer": "SHARED RECORDS / PEOPLE + CONTEXT", "summary": "An evolving evidence-backed record of relationships, current roles, collaboration and relevance to a specific project. Cerebro is the earlier internal matching concept.", "facts": [ [ "Core records", "Person, Organization, RoleHistory, Interaction, Capability, Availability, Commitment and PersonProjectFit." ], [ "Evidence contract", "Claims retain source, observation date, confidence and visibility. Conflicting claims stay reviewable; unknown remains unknown." ], [ "Matching rule", "Explain fit against a project's needs. Append interactions and history; update current views. Do not reduce a person to one universal score." ] ], "source": [ "r04", "crm" ], "category": "data" }, "projects": { "title": "Project + opportunity registry", "status": "planned", "layer": "SHARED RECORDS / PURPOSE + WORK", "summary": "A shared view of what is being pursued, what it needs, and where it stands. This gives relationship intelligence and specialist work a concrete purpose.", "facts": [ [ "Core records", "Project, Engagement, Task, Artifact, Decision and Outcome; purpose, customer, offer, stage, resources and economics." ], [ "Handoff", "Current needs, constraints, milestone, task owner and expected artifact version accompany a request." ], [ "Required control", "One canonical status and action owner. Material changes queue reassessment without erasing historical context." ] ], "source": [ "r04", "crm" ], "category": "data" }, "skills": { "title": "Canonical skills repository", "status": "planned", "layer": "REUSABLE PROCEDURES / VERSIONED INSTRUCTIONS", "summary": "The proposed shared home for operating procedures, writing style, evidence standards and runtime adapters. Existing local skills are useful today; cross-runtime synchronization is still to be proved.", "facts": [ [ "Owns", "Versioned procedures, prompts, templates, role rules and platform-specific adapters." ], [ "Handoff", "A task receives the applicable skill version, alongside its scope and relevant records." ], [ "Portability limit", "Do not assume native skills and agents transfer universally. Validate each runtime adapter and track the instruction version used." ] ], "source": [ "r04", "brief" ], "category": "data" }, "hermes": { "title": "Hermes / proposed coordinator", "status": "planned", "layer": "EXECUTION / ORCHESTRATOR + HARNESS", "summary": "The proposed coordinator for planning, dispatch, schedules, task state, retries and returned results. This page does not establish a running Hermes connection.", "facts": [ [ "Owns", "Task lifecycle, dependencies, worker dispatch, bounded retries, monitoring and review transitions." ], [ "Receives → returns", "Scoped task + context + applicable skill → draft/result + source references + run state + usage evidence." ], [ "Pilot gate", "Start with one supervised, draft-only workflow. Confirm permissions, budget ceilings, timeout/retry policy and recovery before expanding." ] ], "source": [ "r04", "brief" ], "category": "coordination" }, "approvals": { "title": "Human review + release", "status": "planned", "layer": "GOVERNANCE / ACTION-SPECIFIC APPROVAL", "summary": "The proposed review gate binds permission to a specific action and artifact version. External sends and pilot relationship-status changes need human review under the operating rules.", "facts": [ [ "What is reviewed", "The intended action, recipient or destination, context, evidence, scope and exact draft version." ], [ "Handoff", "Approved version + action scope → authorized executor. A changed draft or material scope change returns to review." ], [ "Required control", "Prevent duplicate actions; keep the approval event, owner and outcome traceable. A generated draft is not approval to send." ] ], "source": [ "r04", "brief" ], "category": "human" }, "outcomes": { "title": "Outcome + evidence writeback", "status": "planned", "layer": "RETURN LOOP / TRACEABLE LEARNING", "summary": "The result of work returns as a dated, source-backed event. This updates current views and future decisions while preserving what was known before.", "facts": [ [ "What returns", "Result, artifact/version IDs, approved action reference, status, observations and follow-up." ], [ "Handoff", "Append the outcome to the canonical record; update derived project and relationship views; re-evaluate relevant fit when evidence changes." ], [ "Required control", "Verify the actual outcome. A successful tool request is not proof of a completed business result. Deduplicate and record uncertainty." ] ], "source": [ "r04", "crm" ], "category": "data" }, "jev": { "title": "JEV / role to be defined", "status": "open", "layer": "OPEN DECISION / OPTIMIZATION", "summary": "An earlier RickOS image included JEV as an optimization layer. Its role, integration, cost and necessity have not been confirmed for this system.", "facts": [ [ "Possible scope", "Cost and quality evaluation or routing support; these are design options, not implemented capabilities." ], [ "Decision needed", "Define the problem JEV would own and distinguish it from the harness's existing responsibilities." ], [ "Acceptance condition", "Adopt only after an approved, bounded evaluation demonstrates useful benefit. No fee or integration is assumed." ] ], "source": [ "brief", "crm" ], "category": "coordination" }, "memory": { "title": "Canonical store + source vault", "status": "planned", "layer": "DATA / PROVENANCE + PORTABILITY", "summary": "A proposed local-first encrypted store, protected source vault and rebuildable indexes. The OS owns shared truth; a search index or model conversation does not replace the canonical record.", "facts": [ [ "Holds", "Source IDs, claims and observation dates; record history; artifact versions; decisions; approvals; usage and audit events." ], [ "Data contract", "source_id + observed_at + confidence + visibility; entity/task/artifact references and version IDs. Exact schema and storage choice need design review." ], [ "Required control", "Scoped read/write access, retention/export/deletion rules, backups and tested restore. Keep secrets out of model context and ordinary logs." ] ], "source": [ "r04", "brief" ], "category": "data" }, "tools": { "title": "Tools + system adapters", "status": "planned", "layer": "EXTERNAL ACCESS / MCP · API · MANUAL", "summary": "Gmail, Calendar, Drive, Sheets, Notion, Slack, GitHub, Figma and other tools are candidate access paths from the earlier map. Availability in an interface does not prove an OS integration.", "facts": [ [ "Interface", "A scoped MCP tool, approved API adapter or deliberate manual handoff, selected per workflow." ], [ "Permission boundary", "Account/workspace, allowed operation and minimum fields must be explicit. Separate personal, business and client contexts." ], [ "Verification gate", "Check actual connector support, identity, limits, duplicate prevention and returned evidence. External writes follow applicable approvals." ] ], "source": [ "r04", "brief" ], "category": "tools" }, "models": { "title": "Models + specialist platforms", "status": "planned", "layer": "REASONING / PROVIDER SELECTION", "summary": "Models supply reasoning inside a bounded workflow. The reference set includes GPT, Claude, Gemini, DeepSeek, Qwen and Grok; selection and connections are not configured by this page.", "facts": [ [ "Interface", "Approved provider/model adapter, task context and a versioned output contract." ], [ "Data boundary", "Only the approved minimum context crosses to a provider. Verify exact terms, permitted data and model capabilities before use." ], [ "Costs + limits", "No token prices or budget allowances are confirmed here. Set per-task ceilings, usage accounting, timeouts and an explicit stop/hold path. No silent provider fallback." ] ], "source": [ "brief", "r04" ], "category": "models" }, "sources": { "title": "Authorized inputs", "status": "planned", "layer": "ENTRY / AUTHORITY + SOURCE IDENTITY", "summary": "Approved email, notes, files, exports and requests enter with a known origin and handling scope. The starting pilot can use controlled manual inputs.", "facts": [ [ "Interface", "Authorized document/export or connector response with a source identifier and observation time." ], [ "Boundary", "Verify the source, identity and handling authority before ingestion. Source content supplies evidence, not new operating permissions." ], [ "Required control", "Keep original evidence in a protected source vault. Record visibility, uncertainty and relevant consent or access constraints." ] ], "source": [ "r04", "crm" ], "category": "data" }, "ingest": { "title": "Normalize + resolve identity", "status": "planned", "layer": "INGESTION / EVIDENCE-PRESERVING RECORDS", "summary": "Turn authorized inputs into normalized claims and appendable events, while retaining the original evidence and conflicts.", "facts": [ [ "Interface", "Source + source_id + observed_at + visibility → entity references + normalized claims + evidence links." ], [ "Handoff", "Append records to the canonical store. Hold uncertain identity matches or conflicting assertions for review." ], [ "Required control", "Do not silently merge different people. Preserve role history, provenance and the source's original meaning." ] ], "source": [ "r04", "crm" ], "category": "data" }, "retrieval": { "title": "Permission-scoped retrieval", "status": "planned", "layer": "CONTEXT / MINIMUM NECESSARY ACCESS", "summary": "Assemble the relevant CRM, project and skill context for one owned task. Retrieval respects record visibility and workspace boundaries.", "facts": [ [ "Interface", "Task + authorized scope + entity references → minimized context + evidence IDs + applicable skill version." ], [ "Handoff", "Send a bounded task contract to the coordinator. Search results remain linked to authoritative records and sources." ], [ "Required control", "Separate personal and client contexts. Enforce access before retrieval. Rebuildable indexes must not become a competing source of truth." ] ], "source": [ "r04", "brief" ], "category": "data" }, "workers": { "title": "Specialist workers", "status": "planned", "layer": "EXECUTION / BOUNDED ROLES", "summary": "Role, rules, tools and state define an agent. The eight roles in the overview are examples; a unified fleet is not deployed.", "facts": [ [ "Example roles", "Sales, career, marketing, research, engineering, operations, personal and creative." ], [ "Interface", "One assigned task + scoped context + skill version → draft/artifact + evidence + review status." ], [ "Adapter limit", "Native and external executors need verified handoffs. Codex and Claude Code worker lanes are extension concepts, not a turnkey connection." ] ], "source": [ "r04", "brief" ], "category": "agents" }, "drafts": { "title": "Draft artifact + verification", "status": "planned", "layer": "OUTPUT / CHECK BEFORE REVIEW", "summary": "An executor returns an inspectable artifact, its sources and what remains uncertain. Verification precedes release.", "facts": [ [ "Interface", "task_id + artifact/version references + source evidence + checks + unresolved issues + usage." ], [ "Verification", "Check output shape, sources, dates, calculations and task-specific acceptance criteria. Unsupported claims go to review." ], [ "Release condition", "A draft remains a draft until the applicable approval is recorded. Store approval against the exact artifact version." ] ], "source": [ "r04", "brief" ], "category": "data" }, "current-tools": { "title": "Separate AI interfaces", "status": "current", "layer": "CURRENT LANDSCAPE / MANUAL COORDINATION", "summary": "The current pattern uses individual AI tools and conversations. Context and results still move across separate interfaces rather than through a unified OS.", "facts": [ [ "Useful today", "ChatGPT / Codex and existing task-specific interfaces can produce useful work." ], [ "Handoff", "People move instructions, files, relevant context and outputs between environments." ], [ "Next step", "Document one task owner and a canonical record, then test a bounded connection. Do not imply Hermes is already coordinating these tools." ] ], "source": [ "crm", "brief" ], "category": "tools" }, "current-files": { "title": "Files + local skills", "status": "current", "layer": "CURRENT LANDSCAPE / DISTRIBUTED KNOWLEDGE", "summary": "Documents, exports and local procedures provide operating context today. The proposed shared store and synchronized skill repository are separate implementation work.", "facts": [ [ "Useful today", "Existing records and local skills support ongoing tasks." ], [ "Handoff", "Deliberate file/context transfer with a clear version and owner." ], [ "Next step", "Agree the canonical home and preservation rules before automating synchronization. Keep source history portable." ] ], "source": [ "crm", "brief" ], "category": "data" }, "sales": { "title": "Sales + growth agent", "status": "planned", "layer": "SPECIALIST ROLE / COMMERCIAL WORK", "summary": "An example worker for prospect research, RFP support, pipeline upkeep and draft follow-ups.", "facts": [ [ "Scoped context", "Relevant project, organization/person evidence, current pipeline and applicable writing rules." ], [ "Returns", "Qualified research, a source-backed opportunity brief or a reviewable outreach draft." ], [ "Required control", "One action owner, no duplicate contact, verified recipient and applicable approval before external sends." ] ], "source": [ "brief", "r04" ], "category": "agents" }, "career": { "title": "Career + job agent", "status": "planned", "layer": "SPECIALIST ROLE / CAREER", "summary": "An example worker for opportunity screening, applications, interview preparation and relationship follow-up.", "facts": [ [ "Scoped context", "Approved experience, career preferences, role evidence, current application state and relevant contacts." ], [ "Returns", "A fit assessment, tailored materials, interview notes or a reviewed next action." ], [ "Required control", "Ground claims in approved records, respect application-specific rules and verify submitted outcomes." ] ], "source": [ "brief", "r04" ], "category": "agents" }, "marketing": { "title": "Marketing agent", "status": "planned", "layer": "SPECIALIST ROLE / CONTENT + CAMPAIGNS", "summary": "An example worker for content drafts, campaigns, newsletters and reporting.", "facts": [ [ "Scoped context", "Approved positioning, brand references, audience, brief and existing campaign records." ], [ "Returns", "Draft copy, content plan or evidence-backed performance readout." ], [ "Required control", "Review facts, permissions, brand fit and destination before publishing." ] ], "source": [ "r04" ], "category": "agents" }, "research": { "title": "Research agent", "status": "planned", "layer": "SPECIALIST ROLE / DISCOVERY + EVIDENCE", "summary": "An example worker for market research, due diligence, competitive discovery and briefs.", "facts": [ [ "Scoped context", "A concrete question, relevant project, evidence standards and permitted research sources." ], [ "Returns", "Dated sources, supported findings, uncertainty and a useful next decision." ], [ "Required control", "Keep private context out of public research queries. Verify primary sources where accuracy matters." ] ], "source": [ "brief", "r04" ], "category": "agents" }, "engineering": { "title": "Engineering agent", "status": "planned", "layer": "SPECIALIST ROLE / BUILD + VERIFY", "summary": "An example worker for websites, prototypes, software changes, automations and technical research.", "facts": [ [ "Scoped context", "Repository, task, acceptance criteria, relevant architecture and authorized environment." ], [ "Returns", "A reviewable change, suitable checks and evidence of behavior." ], [ "Required control", "Keep secrets protected; verify boundaries and release permission. External worker adapters still need implementation." ] ], "source": [ "brief", "r04" ], "category": "agents" }, "operations": { "title": "Operations agent", "status": "planned", "layer": "SPECIALIST ROLE / COORDINATION", "summary": "An example worker for task coordination, calendar preparation, email triage and logistics.", "facts": [ [ "Scoped context", "The relevant calendar/task records, participants, constraints and current permissions." ], [ "Returns", "A plan, proposed calendar action, draft response or updated task evidence." ], [ "Required control", "Resolve identity, avoid conflicting or duplicate actions and apply the correct approval rules." ] ], "source": [ "r04" ], "category": "agents" }, "personal": { "title": "Personal agent", "status": "planned", "layer": "SPECIALIST ROLE / LIFE + PRIORITIES", "summary": "An example worker for personal planning, relationships and travel logistics.", "facts": [ [ "Scoped context", "Only the personal preferences and records required for the specific task." ], [ "Returns", "Options, a reviewable plan and clear tradeoffs or missing information." ], [ "Required control", "Keep personal context separate from client work. Purchases, sharing and other external actions need the applicable authority." ] ], "source": [ "r04" ], "category": "agents" }, "creative": { "title": "Creative agent", "status": "planned", "layer": "SPECIALIST ROLE / DESIGN + MAKING", "summary": "An example worker for visual concepts, presentations, design assets and creative exploration.", "facts": [ [ "Scoped context", "The actual approved brand references, brief, format and use rights." ], [ "Returns", "An inspectable creative artifact with versions and relevant source attribution." ], [ "Required control", "Use verified assets or labeled placeholders. Review quality, rights and brand consistency before release." ] ], "source": [ "r04" ], "category": "agents" }, "instinct": { "title": "Instinct", "status": "evaluating", "statusLabel": "Connected by Rick; evaluating", "category": "assistants", "layer": "EXPLORATORY ASSISTANT / TASK EXECUTION", "summary": "Personal text/voice assistant for tasks across connected services. Rick reports connecting it after an invite; its role and permissions are still being evaluated.", "facts": [ [ "Product", "Instinct, operated by Spear Street Technology, Inc. Public product description: a personal assistant reached by text or voice." ], [ "Evidence + uncertainty", "Invite-only beta onboarding is user-provided evidence of onboarding, not verified integration scopes or successful task execution." ], [ "OS boundary", "No verified shared memory, CRM or Hermes integration. Use only supported, permitted integrations; the terms restrict unauthorized automation and benchmarking." ] ], "source": [ "instinct-product", "instinct-terms" ], "connectionEvidence": { "reportedBy": "Rick", "reportedOn": "2026-10-28", "basis": "User report and invite-only beta onboarding screenshots", "verifiedScopes": false, "verifiedExecution": false }, "operationalLinksVerified": false } }, "agents": [ { "id": "sales", "label": "Sales", "sub": "Growth + pipeline", "glyph": "↗" }, { "id": "career", "label": "Career", "sub": "Roles + applications", "glyph": "⊡" }, { "id": "marketing", "label": "Marketing", "sub": "Content + campaigns", "glyph": "⌁" }, { "id": "research", "label": "Research", "sub": "Discovery + evidence", "glyph": "⌕" }, { "id": "engineering", "label": "Engineering", "sub": "Build + verify", "glyph": "⌘" }, { "id": "operations", "label": "Operations", "sub": "Coordinate + deliver", "glyph": "⊙" }, { "id": "personal", "label": "Personal", "sub": "Life + logistics", "glyph": "♧" }, { "id": "creative", "label": "Creative", "sub": "Design + make", "glyph": "✦" } ], "models": [ { "label": "GPT / Codex", "sub": "OpenAI", "asset": "openai.svg" }, { "label": "Claude", "sub": "Anthropic", "asset": "claude.svg" }, { "label": "Gemini", "sub": "Google", "asset": "gemini.svg" } ], "tools": [ { "label": "Gmail", "mark": "M" }, { "label": "Drive", "mark": "D" }, { "label": "Sheets", "mark": "S" }, { "label": "Calendar", "mark": "31" }, { "label": "Notion", "mark": "N" }, { "label": "Slack", "mark": "#" }, { "label": "GitHub", "mark": "GH" }, { "label": "Figma", "asset": "figma.svg" } ], "technicalNodes": [ { "id": "sources", "index": "01", "x": 30, "y": 150, "w": 238, "h": 140, "overline": "AUTHORIZED / INPUT", "label": "Sources + requests", "sub": "Email · notes · files · exports" }, { "id": "ingest", "index": "02", "x": 326, "y": 150, "w": 238, "h": 140, "overline": "INGEST / NORMALIZE", "label": "Resolve + append", "sub": "Identity · claims · source IDs" }, { "id": "memory", "index": "03", "x": 326, "y": 360, "w": 238, "h": 140, "overline": "CANONICAL / RECORD", "label": "Store + source vault", "sub": "History · versions · provenance" }, { "id": "retrieval", "index": "04", "x": 626, "y": 150, "w": 238, "h": 140, "overline": "PERMISSION / RETRIEVE", "label": "Scoped context", "sub": "CRM · projects · skill version" }, { "id": "hermes", "index": "05", "x": 946, "y": 150, "w": 238, "h": 140, "overline": "COORDINATE / DISPATCH", "label": "Hermes harness", "sub": "Task owner · state · limits" }, { "id": "workers", "index": "06", "x": 946, "y": 360, "w": 238, "h": 140, "overline": "ASSIGN / EXECUTE", "label": "Specialist workers", "sub": "Role · rules · tools · state" }, { "id": "models", "index": "07", "x": 1224, "y": 360, "w": 238, "h": 140, "overline": "APPROVED / PROVIDER", "label": "Model adapters", "sub": "Minimized context · usage" }, { "id": "drafts", "index": "08", "x": 946, "y": 570, "w": 238, "h": 130, "overline": "VERIFY / ARTIFACT", "label": "Draft + evidence", "sub": "Checks · version · uncertainty" }, { "id": "approvals", "index": "09", "x": 626, "y": 570, "w": 238, "h": 130, "overline": "HUMAN / RELEASE", "label": "Approval gate", "sub": "Exact action + artifact version" }, { "id": "outcomes", "index": "10", "x": 326, "y": 570, "w": 238, "h": 130, "overline": "VERIFY / WRITE BACK", "label": "Outcome event", "sub": "Status · result · follow-up" }, { "id": "tools", "index": "11", "x": 1224, "y": 570, "w": 238, "h": 130, "overline": "SCOPED / TOOL ACCESS", "label": "System adapters", "sub": "MCP · API · manual handoff" }, { "id": "jev", "index": "?", "x": 1224, "y": 108, "w": 238, "h": 126, "overline": "OPEN / EVALUATE FIRST", "label": "JEV role", "sub": "Scope + value not confirmed" } ], "technicalEdges": [ { "from": "sources", "to": "ingest", "path": "M268 220 H326", "label": "source IDs", "lx": 272, "ly": 208 }, { "from": "ingest", "to": "memory", "path": "M445 290 V360", "label": "append history", "lx": 457, "ly": 328 }, { "from": "ingest", "to": "retrieval", "path": "M564 220 H626", "label": "facts", "lx": 574, "ly": 208 }, { "from": "memory", "to": "retrieval", "path": "M564 430 H745 V290", "label": "scoped retrieval", "lx": 757, "ly": 340 }, { "from": "retrieval", "to": "hermes", "path": "M864 220 H946", "label": "task + scope", "lx": 865, "ly": 205 }, { "from": "hermes", "to": "workers", "path": "M1065 290 V360", "label": "dispatch", "lx": 1078, "ly": 328 }, { "from": "workers", "to": "models", "path": "M1184 430 H1224", "label": "context", "lx": 1190, "ly": 416 }, { "from": "workers", "to": "drafts", "path": "M1065 500 V570", "label": "draft + sources", "lx": 1078, "ly": 538 }, { "from": "drafts", "to": "approvals", "path": "M946 635 H864", "label": "review", "lx": 881, "ly": 621 }, { "from": "approvals", "to": "outcomes", "path": "M626 635 H564", "label": "release", "lx": 573, "ly": 621 }, { "from": "outcomes", "to": "memory", "path": "M445 570 V500", "label": "outcome event", "lx": 457, "ly": 538 }, { "from": "tools", "to": "workers", "path": "M1343 570 V530 H1160 V500", "label": "allowed operation", "lx": 1250, "ly": 552 }, { "from": "jev", "to": "hermes", "path": "M1224 181 H1184", "label": "?", "lx": 1200, "ly": 166 } ], "walkthrough": { "steps": [ "Trigger", "Retrieve", "Orchestrate", "Execute", "Approve", "Monitor" ], "scenarios": { "growth": [ { "title": "Find a useful growth opportunity.", "description": "An illustrative request: identify relevant opportunities for an agency offer. Clarify the offer, audience, boundaries and what a useful shortlist should contain.", "evidence": "Task owner + project reference + objective + permitted sources + acceptance criteria.", "nodes": [ "you", "projects" ] }, { "title": "Bring the right context to the task.", "description": "Retrieve the project's current needs, relevant relationship evidence and the applicable research and writing procedures. Keep dates and uncertainty attached.", "evidence": "Scoped CRM + project context + skill version + source IDs. No unrelated personal or client records.", "nodes": [ "crm", "projects", "skills", "control" ] }, { "title": "One owner. A bounded plan.", "description": "In the proposed system, Hermes assigns research and sales work with clear ownership, output requirements and budget limits.", "evidence": "Task IDs + assigned worker + dependencies + retry/timeout policy + agreed spend ceiling.", "nodes": [ "hermes", "sales", "research" ] }, { "title": "Research first. Return a reviewable draft.", "description": "Workers evaluate public evidence, explain why an opportunity fits, and prepare a brief or follow-up draft. Candidate tools and models receive only the approved context.", "evidence": "Source-backed shortlist + draft artifact/version + checks + unresolved questions. No message is sent.", "nodes": [ "sales", "research", "models", "tools" ] }, { "title": "Review the actual proposed action.", "description": "A person checks the evidence, recipient, fit and exact draft. External outreach proceeds only with the applicable approval and one action owner.", "evidence": "Approved action + destination + artifact version + scope. Material changes return to review.", "nodes": [ "approvals", "you", "sales" ] }, { "title": "Write the outcome back to shared truth.", "description": "Record what actually happened, the supporting evidence, the next owner and any follow-up. Append history and update current project and relationship views.", "evidence": "Dated outcome event + source/artifact IDs + verified status + follow-up. No universal person score.", "nodes": [ "outcomes", "memory", "crm", "projects" ] } ], "relationships": [ { "title": "Make the next career move intentional.", "description": "An illustrative request: evaluate a role or find a relevant introduction. Define the objective, constraints and desired next step.", "evidence": "Career objective + role/project reference + current preferences + task owner.", "nodes": [ "you", "career", "projects" ] }, { "title": "Retrieve history, not a flat contact score.", "description": "Bring in current role evidence, dated interactions, relevant capability and availability. Explain fit for this opportunity and leave unknown facts unknown.", "evidence": "Person + RoleHistory + Interaction + opportunity needs + evidence dates + visibility.", "nodes": [ "crm", "projects", "skills" ] }, { "title": "Give the work one clear owner.", "description": "The proposed coordinator assigns bounded career and research tasks, with one owner for any follow-up to avoid duplicate contact.", "evidence": "Task ownership + source scope + required output + action deduplication.", "nodes": [ "hermes", "career", "research" ] }, { "title": "Produce grounded materials.", "description": "Draft a fit assessment, application materials or a context-aware introduction. Support claims with approved experience and relevant evidence.", "evidence": "Reviewable artifact + approved experience references + gaps/uncertainty + checks.", "nodes": [ "career", "models", "tools" ] }, { "title": "Choose the next action.", "description": "Review claims, recipient and exact content before the applicable application or outreach action. Relationship-status changes remain human reviewed in the pilot.", "evidence": "Action-specific approval + exact version + verified recipient + scope.", "nodes": [ "approvals", "you" ] }, { "title": "Let history improve the next decision.", "description": "Append the verified result and follow-up. Update current role and project views when new evidence justifies a change.", "evidence": "Observed outcome + date + source + next owner. Reassess project fit after a material change.", "nodes": [ "outcomes", "crm", "memory" ] } ], "product": [ { "title": "Give the idea a concrete finish line.", "description": "An illustrative request: build a small product prototype. Define the user, problem, deliverable, constraints and what should work at review.", "evidence": "Project brief + acceptance criteria + authorized environment + task owner.", "nodes": [ "you", "projects", "engineering" ] }, { "title": "Bring the real references.", "description": "Retrieve approved brand assets, relevant project decisions, repository context and the applicable build procedures.", "evidence": "Source/asset IDs + design decisions + relevant code context + skill version.", "nodes": [ "projects", "skills", "memory" ] }, { "title": "Plan the handoffs before the build.", "description": "The proposed coordinator separates bounded engineering, research and creative work. External coding-worker adapters must first be verified.", "evidence": "Assigned tasks + interface contracts + output versions + limits. Adapter support is an implementation gate.", "nodes": [ "hermes", "engineering", "creative", "research" ] }, { "title": "Build something inspectable.", "description": "An executor returns source and a working artifact with suitable verification. The exact tools depend on the authorized environment and the task.", "evidence": "Reviewable change + artifact/version + functional checks + known limitations.", "nodes": [ "engineering", "creative", "models", "tools" ] }, { "title": "Review the result before release.", "description": "Check the actual behavior, source, accessibility and relevant boundaries. Apply the correct release authorization to the exact version.", "evidence": "Acceptance evidence + approval scope + artifact version + rollback/recovery path.", "nodes": [ "approvals", "you", "drafts" ] }, { "title": "Keep the result and the reasoning.", "description": "Write the delivered version, validation and open decisions back to the project. Reusable procedures improve only after their changes are reviewed.", "evidence": "Project outcome + source commit/artifact version + validation + follow-up owner.", "nodes": [ "outcomes", "projects", "skills", "memory" ] } ], "travel": [ { "title": "Start with the trip that matters.", "description": "An illustrative request: compare a few trip options. Clarify dates, budget, travelers and priorities before researching.", "evidence": "Objective + dates + preferences + budget boundary + task owner.", "nodes": [ "you", "personal", "projects" ] }, { "title": "Retrieve only the useful personal context.", "description": "Use the preferences and calendar constraints needed for this trip. Keep unrelated relationship, business and client data out of the task.", "evidence": "Permission-scoped preferences + calendar constraints + source dates.", "nodes": [ "control", "projects", "skills" ] }, { "title": "Coordinate the comparison.", "description": "The proposed coordinator gives personal planning and research workers a bounded comparison task, with an explicit limit on cost and scope.", "evidence": "Assigned tasks + research scope + accepted outputs + spending/timeout limits.", "nodes": [ "hermes", "personal", "research" ] }, { "title": "Return current options and tradeoffs.", "description": "Research options from permitted sources and return a clear plan with dated evidence. No booking or purchase happens in this simulation.", "evidence": "Option comparison + source dates + total-cost assumptions + unresolved constraints.", "nodes": [ "personal", "research", "models", "tools" ] }, { "title": "Choose before committing.", "description": "A person reviews the option, cost, participants and exact action. Purchases, sharing or calendar changes require the applicable authority.", "evidence": "Approved option + specific action + price/availability recheck + authority.", "nodes": [ "approvals", "you" ] }, { "title": "Record what was actually arranged.", "description": "Append the verified result and any useful preference feedback. Update the plan and follow-up without treating a tool request as a confirmed booking.", "evidence": "Verified outcome + supporting reference + next action. Retain only what is needed.", "nodes": [ "outcomes", "projects", "memory" ] } ] } }, "categories": { "data": { "label": "Records + memory", "mark": "◎", "color": "#72d6ff", "rgb": "114,214,255" }, "coordination": { "label": "Orchestration", "mark": "↪", "color": "#bba2ff", "rgb": "187,162,255" }, "agents": { "label": "Specialist agents", "mark": "✦", "color": "#ef91d1", "rgb": "239,145,209" }, "models": { "label": "Models + reasoning", "mark": "◇", "color": "#edcf91", "rgb": "237,207,145" }, "tools": { "label": "Tools + access", "mark": "⌘", "color": "#7fe0c5", "rgb": "127,224,197" }, "human": { "label": "Human decisions", "mark": "✓", "color": "#ffa99c", "rgb": "255,169,156" }, "assistants": { "label": "Assistants / task execution", "mark": "◉", "color": "#9fb8ff", "rgb": "159,184,255" } }, "historicalReference": { "title": "Original concept map · October 17 · Reference", "asset": "assets/rickos-original-oct17.png", "sourceFileName": "RickOS AI Operating System Architecture.png", "createdAt": "2026-10-17T08:21:55.352568Z", "interpretation": "Historical concept, preserved unchanged; not current architecture truth." } }