openworkid.org / changelog
Changelog
Every change to the upstand.work standard is documented here. Schema changes, extension updates, MCP tool modifications, and governance decisions — all public, all versioned, all permanent.
→ Every change is documented
No silent updates. Every schema modification, however small, appears here before taking effect.
→ Breaking changes require an RFC
Any change that breaks existing valid documents must go through a public RFC process with a minimum 30-day comment period.
→ Entries are permanent
Changelog entries are never edited or deleted. If a decision is reversed, a new entry documents the reversal.
Open RFCs
No open RFCs at this time. The standard is in initial release phase.
v0.1.1August 2026
CurrentSchemaMCP
Additive living-profile release. Current work, explicit ask topics, collaboration preferences, and portable artifacts can now be authored, published, exported, and read through MCP without render-time inference.
Added — Living Profile
schema
CurrentWork captures title, summary, goal, audience, collaborators, next step, related experience, provenance, and owner confirmation.schema
AskTopic is explicitly curated. Suggested or derived topics require confirmedAt before public display.schema
Artifact attaches images, documents, links, videos, or publications to a profile, current work, or an Experience Record.schema
isProminent is now the normative selection signal for featured work; renderers no longer infer selection from array order alone.mcp
get_profile now returns confirmed living-profile data, collaboration preferences, and public artifacts. Contact values, private artifacts, and unconfirmed suggestions remain excluded.v0.1.0April 2026
PreviousSchemaExtensionsMCPGovernance
Initial public release of the upstand.work standard. Establishes the five core concepts, the extension system, the MCP server protocol, and the governance model. All subsequent versions will be measured against this baseline.
Added — Core Schema
schema
ProfessionalIdentity root object defined. Five required fields: @context, @type, id, humanProof, experience, verifications, extensions.schema
ExperienceRecord defined. Five narrative fields: context, challenge, contribution, result, learning. All required except learning.schema
PeerVerification defined. Includes verifier name, role, organisation, email domain (never full address), statement, and mutual flag. Withdrawal mechanism included from day one.schema
HumanProof object defined. Methods: email-magic-link, peer-verification-chain, document-verified. Peer verification count is a secondary signal.schema
PortableIdentityExport envelope defined. Includes export metadata, standard version, and a verificationPortabilityNote field that implementing platforms must preserve.schema
Stable URI structure defined:
upstand.work/{username}/exp/{id} and upstand.work/{username}/ver/{id}. URIs are permanent once published.schema
Writing style variants formalised:
"direct", "grounded", "expert". Stored as metadata on ExperienceRecord, not as a schema constraint.schema
Visibility states defined:
"public" (default, indexed), "unlisted" (accessible via link, not indexed), "inactive" (not accessible, not indexed), "deleted" (404).Added — Extension System
extension
Extension schema defined. Each extension has a canonical URI, a semver version, and a
fields object. Unrecognised fields must be preserved on import.extension
regulatoryNotice field defined for regulated professions. When present in an extension definition, implementing platforms are required to display it during profile editing.extension
Initial reference library published with 19 generated schemas spanning technology, finance, legal, healthcare, creative work, consulting, HR, engineering, education, and sales. All are versioned independently at v1.0.0.
extension
Regulatory compliance notices authored for regulated professions. DE jurisdiction: HWG (Ärzte, Psychotherapeuten), BRAO (Anwälte), Architektenkammer.
extension
RateRange type defined and reused across business extensions: { min, max, currency, unit }. Unit values: "hour", "day", "month", "project".Added — MCP Server
mcp
MCP Streamable HTTP endpoint published at
https://upstand.work/api/mcp. Protocol version 2026-07-28 with stateless 2025-11-25 compatibility.mcp
Production tools:
get_profile and get_verifications. Both are public, read-only, and restricted to profiles whose owners enabled MCP visibility.mcp
Contact details, verifier email addresses, pending confirmations, and withdrawn confirmations are excluded from every MCP response.
mcp
Write tools, authenticated profile suggestions, market benchmarks, and profile search remain roadmap items and are not advertised as available capabilities.
mcp
REST fallback published at
https://upstand.work/api/v1 for environments without MCP support.mcp
Public read limit established at 100 requests per minute per IP. Responses expose the remaining allowance and return
Retry-After when limited.Governance
governance
Standard published under MIT License. Repository:
github.com/entwicklerherz/openworkid.org. Schema hosted at https://openworkid.org/v1.governance
Phase 1 governance declared: upstand.work controls the schema. All changes via public GitHub PRs. Transition to Steering Group when 3–5 external platforms adopt the standard.
governance
Changelog policy established: all entries are permanent, breaking changes require a 30-day RFC, entries are never silently edited.
governance
Employer verification policy published: Verified Employers may only confirm historical employment facts. Refusal to confirm a factually correct tenure results in immediate and permanent loss of Verified Employer status.
v0.2.0Planned — Milestone 2
PlannedSchemaMCPGovernance
Adds write-capable MCP tools, Verified Employer Program schema, market benchmark data types, and the structured contact request protocol. No breaking changes to existing v0.1.0 documents.
Planned additions
mcp
M2 tools go live:
add_experience, request_verification, get_market_benchmark.schema
VerifiedEmployer object defined. Bidirectional employment verification. Employer can confirm tenure facts — never performance, never reasons for departure.schema
ContactRequest schema defined. Structured inbound request channel with mandatory fields: type, budget, context.schema
MarketBenchmark type added to spec. Fields: p25, p50, p75, sample_size, data_source, currency.extension
Community RFC process opens for new extension proposals. First external-authored extensions expected.
governance
Steering Group formation if adoption threshold reached (3–5 external platforms).
v1.0.0Planned — Milestone 3
PlannedStableFoundation
First stable release. Schema is considered production-ready. Breaking changes from this point require major version bump and a minimum 90-day migration window. Governance transitions to Foundation.
Planned additions
mcp
search_profiles tool goes live. Client Auth only. Opt-in profiles only.schema
VerifierReputation object added. Weighted verification scoring based on verifier's own verification history, report history, and account age.governance
Standard transferred to independent Foundation. upstand.work retains the reference implementation. No single entity controls the schema.
governance
Enterprise Verification Infrastructure licensing defined. Large organisations may run the verification protocol internally under an enterprise license.
—RFC Process
All schema changes go through a lightweight RFC process. The bar for non-breaking additions is low. The bar for breaking changes is high.
Non-breaking additions
New optional fields, new extension library entries, new MCP tools. 7-day comment period. Merged if no objections from existing adopters.
Breaking changes
Removing required fields, renaming keys, changing type constraints. 30-day comment period minimum (90 days post v1.0.0). Requires Steering Group approval when active.
01
Open a Discussion on GitHub
Describe the problem, not the solution. What existing use case is not covered?
02
Submit a PR with schema changes
Use the RFC template in
/rfcs/. Include field definitions, example JSON, and migration notes if breaking.03
Comment period
7 or 30 days depending on impact. All adopters are notified. Comments are public and permanent.
04
Merge and changelog entry
Merged changes appear in the next release. A changelog entry is written before the merge, not after.
—Version Policy
MAJOR
Breaking
Removes or renames required fields. Changes type constraints on existing fields. Existing valid documents may no longer validate.
MINOR
Non-breaking
Adds optional fields, new enum values, new extension library entries. All existing documents remain valid.
PATCH
Clarification
Documentation corrections, example updates, typo fixes. No schema changes. No migration required.