Shared Context
Current product state
Section titled “Current product state”Today, the live product is still centered on CareerClaw.
That means the most important thing for the docs to communicate right now is the direction, not a false claim that a full cross-skill shared-context system is already live.
The problem
Section titled “The problem”A multi-skill platform cannot scale by dumping every interaction into one giant conversation.
That would blur:
- skill boundaries
- trust boundaries
- workflow state
- user expectations
The ClawOS direction
Section titled “The ClawOS direction”ClawOS keeps skill-local workspaces and promotes only selected, useful facts into shared platform context.
The intended rule is:
- work stays focused inside the active skill
- useful facts may be promoted upward
- future skills should consume selected context, not raw history dumps
Why the docs should be careful here
Section titled “Why the docs should be careful here”The current codebase already has platform shell, identity, session, and worker boundaries that are multi-skill-friendly.
But the docs should stay honest:
- the platform is designed for shared context
- the docs should not imply a fully shipped cross-skill memory layer if it is not live yet
That honesty matters for trust.