Vision

Where CanDoMore is going.

The idea behind CanDoMore, how it differs from agents, and what it could become for the software you build.

1A new software primitive

Software modeled everything, except the professional.

For decades, software has modeled customers, documents, projects, payments, code and transactions. Yet the person who actually holds the expertise and the relationships is still just a profile, an account, an employee record.

CanDoMore changes that. It makes the professional a first-class software object, persistent, permissioned, with context, memory, relationships and authority.

The professional is the next system of record. CanDoMore is building it.

2A different primitive

Agents act. Identity represents.

General agentCanDoMoreDifference
Responsibility / taskProfessional IdentityThe durable object is the professional, not only a task.
Goal → tools → actionsContext → authority → representationThe response depends on who is asking and what relationship/context applies.
Agent memoryIdentity-level contextThe same Identity can persist across professional channels.
ExecutionRepresentation + governed executionSpecialized agents can eventually operate beneath the Identity.

Agents make software capable of acting. CanDoMore makes you representable inside it.

3For developers

Identity, as an API.

Long term, CanDoMore exposes the professional Identity as infrastructure. Your app can understand professional context and request authorized actions, without rebuilding context, memory and permissions from scratch.

Future directionAgents become the hands. The Identity remains the professional.

Conceptual API
  • /identities
  • /context
  • /memory
  • /relationships
  • /permissions
  • /actions

    

  







  

    
Continuity, by design.

    
Be represented. Never replaced.

    

      Join the first cohort→
      See how it works