FOUNDATION / CURRENT WORK
Keep useful work moving.
Use existing interfaces and skills. Establish canonical records, source IDs and a clear owner for each action.
EXIT One reliable record + review loop.THE PATH TO IKIGAI_OS
RickOS_
Intention. Into motion.
People, intelligence and execution.
One connected view of the system we’re building.
WORKING ARCHITECTURE
A personal operating system.
A foundation for something bigger.
COMPONENT KEY
THE WHOLE PICTURE
One shared truth.
One execution layer.
The intended system. Hermes coordinates work; the OS owns records, rules and decisions. Connections below are proposed.
01 / SHARED TRUTH PLANNED
History is appended.
Current views evolve.
Current views evolve.
INTENT ↓ ↑ RESULTS
02 / SPECIALIST AGENTS EXAMPLE ROLES
03 / INTELLIGENCE CHOSEN PER TASK
THE RETURN LOOP
04 / TOOLS + SYSTEMSSCOPED ACCESS / MCP · APIs · MANUAL
CURRENT PATTERNCapable tools.
Capable tools.
Context still travels by hand.
Work is spread across separate AI interfaces, conversations and files. The shared control plane and Hermes connection remain the design direction.
← →MANUAL HANDOFFS
← →FILES + CONTEXT
THE BRIDGE
Own the records. Scope the context. Prove one workflow.
Then connect what earns its place.
Current patternPlanned connectionOpen decisionEvaluating
Select a component to open its field notes.THE INFORMATION SYSTEM
Follow the evidence.
Respect the boundaries.
A deeper view of ownership, handoffs and data boundaries. Select any component. Drag the canvas or use the zoom controls.
Tab through nodes to inspect without dragging.One task owner · version-specific approval · traceable writeback
EXPLORATORY / OUTSIDE OS FLOWS
Assistants / task execution
Rick reports connecting Instinct after an invite. Invite-only beta onboarding does not establish actual integration scopes or successful execution.
No verified shared memory, CRM or Hermes integration.
Use only supported, permitted integrations. Instinct’s terms restrict unauthorized automation and benchmarking.
FOLLOW A PIECE OF WORK
From an ask to an outcome.
01 / TRIGGER
THE HANDOFF
01 / 06
BUILD SEQUENCE
Prove the loop. Then expand.
BOUNDED PILOT / PLANNED
Connect one workflow.
Test Hermes on a supervised, draft-only task. Add scoped context, approval records and measured cost limits.
EXIT Useful results within an agreed cap.EXPANSION / CONDITIONAL
Add what earns its place.
Introduce more agents, adapters and automation after quality, recovery, permissions and economics are verified.
EXIT Evidence of value before more autonomy.THE EARLIER LANDSCAPE
Original concept map
The earlier RickOS vision, preserved unchanged. Its assumptions and roadmap are historical; the labeled architecture above is the current working blueprint.
FIELD NOTES
What’s decided. What’s still open.
Architecture decisions
- The OS owns canonical records, permissions, policies and approvals.
- Hermes is the proposed execution coordinator. A second orchestrator is not assumed.
- History is appended; search indexes can be rebuilt from the canonical store.
- Person-to-project fit is explained with evidence. There is no universal person score.
- Agents get the minimum context needed. External actions need the applicable human approval.
Costs, limits and open decisions
No operating budget, provider allowance, infrastructure quote or token ceiling has been confirmed for the unified OS.
- Choose the canonical store, source vault, backup and recovery approach.
- Define per-task budgets, retry limits, timeout behavior and the stop condition.
- Verify model/provider terms, rates and context limits at implementation time.
- Confirm JEV’s scope and whether it adds value beyond the harness.
- Prove skill synchronization and external Codex / Claude Code worker adapters.
Security and verification gates
- Resolve identity, permission and visibility before retrieval.
- Separate personal, business and client contexts.
- Validate source IDs, dates, output shape and numerical claims.
- Hold conflicting or unsupported claims for review. Unknown stays unknown.
- Deduplicate actions and assign one canonical owner.
- Approve the exact action/artifact version, record the outcome and test reversible recovery.
REFERENCE SET
01 IKIGAI blue-glow R04Approved visual direction / 28 Oct 2026INTERNAL
02 Rick OS + Hermes briefRecord / execution separation / Oct 2026INTERNAL
03 SWOT architecture presentationInteraction and explanation referenceINTERNAL
04 CRM architecture explorationHistory, project fit and current-state directionINTERNAL
App marks identify referenced products. Text marks are used where a verified logo was unavailable. A mark or connector line does not indicate a running integration.