Open Workplace Profiles

Status: Candidate Profile contract for open-workplace/0.2-draft

A Profile explains how one implementation represents and resolves the responsibilities in the Open Workplace Protocol. The Protocol owns shared semantics; the Profile owns concrete vocabulary, discovery, schemas, projections, validation and declared limits.

Required disclosure

A Profile targeting this draft must state:

Identity

Profile identifier and version;
exact protocol identifier;
publisher and status;
how the Profile itself is obtained with provenance.

Declaration and discovery

what marks a Workplace declaration;
where discovery starts, how it proceeds and where it stops;
behavior for invalid candidates, symlinks and nested boundaries;
which roots or external systems discovery is forbidden to inspect.

Sources and authority

how a Workplace identity and owner are declared;
how Source owner, responsibility, provenance and authority are represented;
composition and conflict rules;
which content is temporary, durable, current or inactive;
how human acceptance and external observations are recorded, when supported.

Projections and resolution

which outputs are Projections;
how consumers recover their Sources;
how drift and output collisions are detected;
the conceptual or serialized Resolved Workplace Context;
the meaning of candidate, resolved, degraded and ambiguous in the implementation.

Relationships and effects

how external authorities and Relationships are represented;
how a Relationship is revalidated;
which authority remains external;
how intended, attempted and observed effects are distinguished.

Operation and validation

static degraded behavior;
validation entry points;
unsupported responsibilities and failure behavior;
implementation extensions and their owners.

Profile freedom

A Profile may define any nouns, hierarchy, cardinality and storage form it needs. Home, Member, Desk, Room, Meeting, Occupant, Role, Equipment, Site and Route are examples from the Endroit Profile, not Open Workplace objects.

A Profile need not provide a lossless mapping to another Profile. It must not claim that a local object is universal, or silently invent an equivalent when another implementation has no matching responsibility.

Minimal Profile document

# <Profile name>

Profile identifier:
Profile version:
Target protocol: open-workplace/0.2-draft
Publisher:
Status:

## Declaration and discovery
## Sources, ownership and authority
## Resolution and conflicts
## Projections
## Material transitions
## Relationships and external effects
## Degraded operation
## Validation
## Extensions and limits

The Protocol does not require this Markdown layout. It requires the disclosed responsibilities.

Endroit as the first observed Profile

Endroit is a Workplace-first application framework and the first observed implementation. Its qualified local endroit/0.10 release candidate targets this draft but is not yet published or deployed. It maps:

Open Workplace responsibility	Endroit representation
Workplace declaration	`WORKPLACE.md`
Human identity	Member documents
Local personal continuity	optional Desk documents
Durable domains	Room documents
Reusable methods	Equipment sources and projections
Material	owned Markdown and registered Artifact documents
External authority	Site declarations
Relationship	Route documents
Local address	rebuildable Checkout materialization
Provider context	generated `AGENTS.md`, `CLAUDE.md` and Skills
Derived resolution	`ResolvedWorkplace` and local build receipt

These names and paths are Endroit-owned. Open Workplace does not require another implementation to expose any of them.

Endroit’s Work Resolution, Artifact kinds, checkout modes, CLI, HUD and provider integrations are extensions. Their presence is not evidence of cross-Profile interoperability or protocol conformance.

Comparison without false equivalence

With only one observed Profile, comparison is a design exercise rather than a portability guarantee. A future comparison should classify each responsibility as:

Result	Meaning
`direct`	Both Profiles preserve the responsibility and authority boundary.
`composed`	Several source concepts represent one target responsibility without loss.
`split`	One source responsibility maps to several target responsibilities.
`lossy`	The target cannot preserve a distinction.
`unsupported`	The target declares no representation.
`ambiguous`	Evidence cannot establish a safe mapping.

A comparison must keep Source provenance, name lost distinctions and avoid mutating either implementation. A proposed transposition remains Material until the human authorizes its application.

Claims this draft does not make

Publication of a Profile does not establish:

certification or conformance;
automatic compatibility with another Profile;
a registry or preferred implementation;
lossless conversion;
authority to inspect or mutate a Workplace;
authority to affect an external system.

A second independently designed implementation and explicit behavioral tests are prerequisites for any future interoperability claim.