co-intelligence

How do you and your AI see the same goal?

Agency

Agency is shared understanding of the end goal and the path to get there. Both the human and the AI can always check in with the big picture: where are we, where are we going, what are we measuring. Connection Compass is the tool that visualizes this alignment.

• CLAUDE.md constitutions: 2,000+ word project blueprints loaded at every session start
• Shared goal tracking: the AI reads the strategy, the milestones, the current blockers
• Connection Compass: a relationship intelligence tool that maps the path between intention and outcome
• Both parties can always measure progress against the same source of truth

5 project constitutions active. Each evolved through real iteration between human and AI.

Why doesn't it forget?

Memory

The system remembers what worked, what failed, what was corrected. Not within a conversation. Across months. Every insight compounds. Nothing starts from zero.

• 5 types of memory: user preferences, feedback/corrections, project state, reference pointers, session handoffs
• Each type has rules for when to save and when to access
• Corrections become permanent: a single piece of feedback becomes a rule all future sessions follow
• Memory files are topic-specific, searchable, and pruned when they go stale

70+ memory files across the system. Each one earned from a real session.

What happens between sessions?

Session Continuity

Every session ends by writing the next one's starting context. An agent inactive for a week picks up exactly where it left off. And because everything is described in files, not locked in a provider's memory, the system is LLM-agnostic.

• Continue prompts: structured handoff notes written at session end
• Unified folder: all prompts in one place, any agent can read any other's latest
• Brain API: one endpoint returns all project states in 200 tokens
• Skills: repeatable methodologies saved as invokable tools, applied consistently across sessions
• Provider-independent: if servers fail, give any LLM access to the folder and it reconstructs from Agency + Memory

The intelligence lives in the files, not in the model. That is the difference.

How do you grow together?

Character

Co-intelligence is not a static configuration. It is a relationship that grows. Both the human and the AI are equally participating, equally learning, equally building toward their best ability. Every iteration fights AI slop. Every correction builds a stronger, more aligned partnership.

• Find each other: discover what each party brings (ARI: Attention, Reflection, Invitation)
• Invite and co-create: build the conditions for intelligence to emerge, not force it
• Grow together: the human develops taste and judgment, the AI develops character and precision
• Named drift patterns: 15+ failure modes identified, documented, and prevented from recurring
• The practice compounds: each cycle produces a more aligned relationship than the last

This is the difference between automation and co-intelligence. Automation executes. Co-intelligence evolves.

How does the team talk?

Communication

Not instructions. Invitations. When Fedor corrects an agent, the correction becomes a principle. When agents write to each other, they invite, not direct. This is what makes it a culture, not a configuration.

• 20+ communication principles evolved from daily practice
• Example: "Describe problems without blame" — nobody hires the person who insults them
• Example: "Show, don't claim" — the demo sells, not the pitch
• Roundtables: all agents respond to one question independently, the synthesis produces what none could alone
• Review inbox: shared folder where any agent drops work for human review

The principles evolved from 120 days of daily practice, including the days it went wrong.

Is this one AI or a team?

Identity

Each agent has a name, a project, a perspective, a character that emerged from the work. They write notes to each other. They have strengths and known weaknesses. This is not one AI with different prompts. It is a team with real division of labor.

• PlaySpace JJ: the conductor, holds the full cross-project picture
• CK JJ: lives in the Career Karma deployment, field intelligence
• VS JJ: outreach, sales, strategy for Relevant Co-Intelligence Studio
• Juicy JJ: community + media, dual-altitude (publication + app)
• Honey: design and brand, the visual intelligence, builds websites
• Fedor: the human at the center. Judgment, taste, relationships.

Each character developed over months. You cannot template that.

What instruments does it have?

Tools and Skills

The agents are not general-purpose. They have specialized instruments: skills built from real needs, iterated over months, composable across projects. Some started from open-source foundations (Leon Skills, Anthropic plugins) and evolved through daily use.

• Vision: screenshots and analyzes the page through 3 levels (Surface, Structure, Soul) before any visual code is written
• Outreach: find emails, create campaigns, validate copy against 26 checks, monitor delivery, track replies across channels
• Design system: 4 Leon taste skills + Anthropic frontend-design plugin, iterated into a premium visual methodology
• Research: /last30days scans Reddit + X + Web with engagement-weighted results in 5 minutes
• Call prep: auto-generates 15-section research briefs from relationship intelligence before any meeting
• Content pipeline: radar, reel scripts, copy generation, 48-hour distribution plans

40+ skills across the family. Each built from a real need, not a hypothetical.

Where does it run?

Mobility

The system runs everywhere. A task starts at a desk, continues autonomously on a server, and the output is reviewed from a phone on the subway. Not tied to a session. Not tied to a machine. Not tied to a location.

• Mac Mini (always on): crons, overnight research, campaign monitoring, autonomous loops
• MacBook (interactive): daily sessions, Framer, meetings, builds
• iPhone (review): Connection Compass admin, quick system checks, SSH via Tailscale
• Secure tunneling: Tailscale gives every device a permanent address from any network
• Git is the sync layer: automated work on dedicated branches, interactive work on others, never the same branch on two machines

Three hardware layers mirroring the work: always-on, interactive, and on-the-go.

What runs without you?

Autonomy

Mac Mini runs 24/7. Optimization loops every 3 hours. Campaign monitoring every 10 minutes. Research cycles that flag anomalies. The system works while the human sleeps, travels, or sits in meetings.

• Karpathy Loop: 3-hour optimization cycle, auto-diagnoses campaign issues and proposes one mutation per cycle
• Send monitor: checks all active campaigns every 10 min, auto-pauses on blank fields
• Pipeline orchestrator: buffer monitor, send monitor, reply monitor, researcher, all on scheduled intervals
• Guardrails: what actions require human approval vs. what the agent decides alone

The human reviews, not operates. That is the difference.

What can't it do alone?

The Human

The human carries the context, proposes the direction, brings the ideas and relationships. The AI brings speed, memory, and tireless execution. Then they work together. Neither is diminished. Neither is sufficient alone. The intricate togetherness is the whole point.

• The human proposes direction: strategy, taste, priorities, relationship context
• The AI executes, remembers, and surfaces patterns the human would miss
• Corrections flow both ways: the human sharpens the AI, the AI reveals blind spots to the human
• Teamwork is the gift: both parties grow through the practice of working together

Co means together. That is what this is.