A free personal workspace for keeping questions, evidence, analysis, decisions, and structured thinking connected from the beginning of an inquiry through its outcome.
From difficult question to a decision you can trace.
Workspace keeps the basis of the work visible as it develops. Sources remain connected to evidence, evidence to analysis, analysis to choices, and choices to the reasoning that supports them.
01Research
Frame questions, collect sources, and keep the inquiry organized.
02Evidence
Preserve support, provenance, and links back to the source.
03Analysis
Make datasets, methods, assumptions, comparisons, and findings visible.
04Decision
Compare options, weigh criteria, assess risk, and record rationale.
05Canvas
Map systems, relationships, stakeholders, claims, and ideas.
Connected reasoning across every stageQuestionsSourcesProvenanceAssumptionsMethodsTrade-offsDecisions
WORKSPACE PATHWAYS
Begin with the work in front of you.
These are connected ways to use one personal environment, not separate products or locked tiers. A project can move between them as the work develops.
01
Research and evidence
Investigate a question, organize sources, extract evidence, map claims, and preserve provenance.
Sources + evidence02
Analysis and modeling
Register datasets, variables, assumptions, methods, comparisons, and findings.
Analytical record03
Decision and trade-offs
Compare alternatives, criteria, uncertainty, risks, mitigations, and rationale.
Decision record04
Systems and structured thinking
Use Canvas boards to arrange relationships among evidence, analysis, decisions, systems, and stakeholders.
Structured synthesis05
Connected tools and reusable artifacts
Move stable project context into Sustainable Catalyst tools and return structured artifacts to the originating project.
Search canonical objects across projects, inspect provenance and references, discover related work, and organize reusable collections.
Cross-project local index07
Import and interoperability
Stage outside files locally, review provenance, and move structured artifacts into or out of Workspace without silent overwrite.
Portable interchange08
Share and portable projects
Create integrity-checked whole-project copies or static review snapshots without cloud sync, public links, or live collaboration.
Portable project
PERSONAL CAPABILITY
A serious working environment, free to use.
Workspace is useful on its own. Institutional capabilities belong in Catalyst Intelligence because the operating context changes, not because the personal product is intentionally weakened.
LOCAL FIRSTYour work stays with you.
Guest use remains device-local. Signed-in users may opt into explicit project backups for recovery without background sync.
VISIBLE REASONINGKeep the basis of the work attached.
Sources, evidence, assumptions, methods, findings, options, and rationale remain connected inside the project.
CONNECTED BY DESIGNUse specialized tools when they help.
Workspace can pass privacy-minimized context to the wider Sustainable Catalyst system and accept structured returns.
IDENTITY & PERSISTENCEUse Workspace immediately. Add identity when it helps.
No login wall. Signing in does not upload project content; each cloud backup requires an explicit action.
WORKSPACE APPLICATION
Open the working environment.
Projects hold the work; Personal Knowledge and Graph connect it across projects; Activity and History make workflow state, next actions, and named restore points inspectable; Import, Share, and connected tools move work deliberately; optional account backup/sync add off-device recovery while local diagnostics keep the persistence boundary explicit.
Local-first by defaultWorkspace remains fully usable without signing in. Projects are stored on this device. Sign-in is optional. Account recovery and cross-device sync are optional. Backups require an explicit action, sync requires explicit per-project enrollment, and nothing synchronizes in the background. Connected tools can return structured work to the originating project through the established local-first handoff contract. Research Notebook remains inside the same project boundary and does not upload or invoke AI automatically. Workspace 1.x keeps these boundaries explicit while improving the working interface.
Storage & identitySaved on this deviceManage
IDENTITY & PERSISTENCE
Identity is optional. Your project storage boundary stays explicit.
GUESTGuest WorkspaceYour work is associated only with this browser device.
ACCESSNo account requiredAnonymous use remains a first-class path.
PERSISTENCELocal first · optional backup/syncBackups are explicit. Sync is opt-in per project and never runs in the background.
DEVICE IDInitializing…Pseudonymous local identifier; no personal data is encoded.
Sign-in keeps local work available and unlocks explicit account recovery plus opt-in per-project sync. Sign-in alone uploads nothing.
ACCOUNT CLOUD RECOVERY
Back up deliberately. Restore without overwriting local work.
LOCAL ONLY
Account recovery is optional and account-bound. Manual backups remain restore-as-copy. Sync below is separately enrolled per project and uses revision checks rather than silent overwrite.
Sign in to use account recovery and explicit sync. Local Workspace remains fully available without an account.
CROSS-DEVICE SYNC
Synchronize deliberately. Never hide a conflict.
LOCAL ONLY
Sync is opt-in for each project and runs only when you choose an action. Workspace compares SHA-256 project fingerprints and server revisions before pushing or pulling. If both sides changed, neither copy is overwritten automatically.
LOCALChoose project
CLOUDNo cloud head
COMMON BASENo common revision
STATEDISABLED
Sign in to enable explicit cross-device sync. Guest/local Workspace remains fully available.
Production continuity planNot checked
Check status to derive an explainable local/cloud action plan. Workspace never applies the plan automatically.
Local-first continuity, not cloud-first storageEnabling sync stores local enrollment metadata only. Project content moves only after an explicit Sync now or conflict-resolution action. Continuity plans and receipts contain metadata/fingerprints, not project content or device identity. Shared team sync and institutional storage remain outside Workspace.
Device migration & interrupted-sync recoveryMigration files preserve project content and a sync baseline, never device identity or automatic enrollment.
Migration imports always create a new local copy. Sync must be enrolled again explicitly on the receiving device.
LOCAL HEALTH & RECOVERY
Inspect the browser boundary before it becomes a problem.
NOT CHECKED
Diagnostics run only in this browser. The exported diagnostic report contains capability/status metadata, not project content, object text, URLs, or the local device identifier.
STORAGENot checkedBrowser-local persistence availability and current-state serialization.
RECOVERYNot checkedLast-known-good local snapshot availability.
INTEGRITYNot checkedSHA-256/Web Crypto support for portable package verification.
WORKSPACE SIZENot checkedApproximate local serialized state size; no content leaves the browser.
No diagnostic run has been performed.
PUBLIC BETA / FIELD DIAGNOSTICS
Capture the environment when something goes wrong.
LOCAL REPORT
Field checks measure browser capability, storage/recovery state, workspace size, serialization latency, and interface density. Reports are created locally. Nothing is submitted automatically, and project content is never added unless you type it into the issue form yourself.
RUNTIMENOT CHECKEDBrowser and core capability status.
DOM DENSITYNOT CHECKEDRendered Workspace element count.
ATTENTIONNOT CHECKEDExplicit threshold flags; never a hidden score.
No field check has been run. Reports stay on this device until you explicitly export them.
Workspace recovery modeA damaged local state was isolated and a clean workspace was opened.
Workspace / HomeHome
Resume active work, orient a project, or move directly to the next task.
Workspace controlsNavigate quickly, adjust density, or review terminology and shortcuts.
WORKSPACE COMMANDS
Go directly to the work.
ORIENTATION
One Workspace, five primary areas.
The primary navigation stays deliberately small. Specialized tools appear within Research, Review, and Exchange rather than competing at the top level.
On compact or touch devices, Workspace prioritizes capture, review, and lightweight editing. Dense graph, comparison, and composition surfaces remain available and use bounded scrolling instead of forcing the page wider.
⌘/Ctrl + KOpen command palette
Alt + 1…5Open Start through Exchange
/Focus search in the current view
EscClose Workspace dialogs
ProjectThe canonical local container for a body of work and its structured objects.
ResearchRetrieval, Notebook, Knowledge, citations, composition, and Graph exploration.
NotebookWorking notes, source captures, links, synthesis, and grounded questions.
KnowledgeA derived view over canonical records for finding and reusing existing work.
ReviewActivity, lifecycle, history, changes, reconciliation, safety, and audit.
ExchangeDeliberate import, collaboration, institutional handoff, and sharing.
SAFE ACTION PREFLIGHT
Review before proceeding
Workspace is preparing an explicit change review for this action.
WORKSPACE HOME / PROJECT COCKPIT
Return to the work in front of you.
Home summarizes active projects, recent work, research context, and deterministic next actions without turning Workspace into a dashboard of hidden scores. Start new work only when you need it; otherwise continue directly from the project cockpit.
STABLEv2.0.3
PROJECT COCKPIT
One place to orient the active project.
No active project yet. Create or open a project to populate the cockpit.
ACTIVE PROJECTNone selectedLocal workspace
0Active projects
0Objects
0Research records
0Notebooks
CONTINUE
Choose a project
Your next action is derived only from visible project state.
WORK MODES
Move inside the active project.
Context, not scoring.The cockpit uses only local project state to summarize work and suggest explicit routes. It does not infer productivity, rank people, upload content, or run AI automatically.
FIRST RUN / YOUR FIRST PROJECT
Name the work and choose only as much structure as you need.
Workspace creates the project locally after you submit this form. You can start blank or begin with an editable guided workflow; nothing is inferred, completed, uploaded, or enrolled in sync automatically.
Each quick start creates a new local project and opens an editable guided workflow. Nothing is inferred, completed, or uploaded automatically.
RUNTIME STATUS
Know what this browser can support.
LOCAL STORAGEChecking…
INTEGRITYChecking…
FILE IMPORT / EXPORTChecking…
RETURN HANDOFFSChecking…
Running local capability checks…
RECENT WORK
Continue where you left off.
No local projects yet. Start a blank project or choose a guided pathway above.
Workspace operating boundaryGuest use remains first-class. Sign-in is optional. Cloud backup and sync stay explicit. Lifecycle states remain human-declared. Workspace does not run behavioral telemetry or assign readiness/productivity scores.
PUBLIC PRODUCT BETA III / PRODUCT JOURNEY
Test the whole path from discovery to deliberate handoff.
Beta III treats Workspace as one product journey rather than a collection of features. Run the local topology check, then walk the nine stages yourself. Manual review marks live only in this browser session and never alter a project.
Checklist, not a score.Workspace does not infer that you succeeded because a route exists or because you marked a stage reviewed. No behavioral telemetry, automatic completion, project mutation, lifecycle advancement, or automatic submission is introduced. The exported report contains route/topology state and session review marks only.
PRODUCT HELP / RECOVERY GUIDANCE
Understand the boundary before you repair the work.
Workspace help explains how the product behaves, where work is stored, and which recovery path is safest. Guidance is advisory only: it does not repair, restore, upload, synchronize, or alter a project automatically.
Local-first remains the default.Guest projects live in this browser. Signing in does not silently upload project content. Backup, sync, import, restore, review reconciliation, and institutional transfer remain explicit actions.
LOCALBrowser-local firstDo not clear browser storage until important work has a verified portable or recovery copy.
BACKUPExplicit recovery copyAccount backup is separate from sync enrollment and does not create background synchronization.
SYNCConflict-safe, user initiatedWorkspace rejects silent last-write-wins when local and cloud revisions diverge.
RESTOREPrefer restore-as-copyCompare the recovered state before deleting or replacing any existing local project.
Loading Workspace help…
Product help is available locally.
If Workspace appears damaged:Preserve evidence first. Export a project/recovery candidate when possible, inspect Persistence Integrity, use Recovery Drills only as a simulation, and avoid clearing browser storage until a separate verified copy exists. A WordPress/plugin error is a site-runtime issue and should be diagnosed separately from browser-local project recovery.
INTEGRATED KNOWLEDGE WORKSPACE
Research without feature boundaries.
Search Notebook material, canonical Workspace Objects, and Research Workspace questions and claims through one derived index. Every result remains anchored to its original record; this view does not duplicate content or invent semantic relationships.
0research records
0Workspace objects
0Notebook records
0questions & claims
FOCUSED RESEARCH WORKSPACE
Choose the tool needed for the work in front of you.
Research no longer opens every subsystem in one continuous page. Search, organize, reference, review, and compose in focused surfaces while the selected canonical research context remains available across the session.
UNIVERSAL WORKSPACE SEARCH
Find the work, not the subsystem.
Search projects, canonical objects, notebooks, research, analysis, decisions, briefing drafts, citations, and explicit research tasks from one local index. Ranking remains deterministic and inspectable—no embeddings, hidden personalization, or query telemetry.
0matching records
DYNAMIC RESEARCH VIEWS
Organize retrieval without copying research.
Smart collections store explicit retrieval definitions. Saved views add grouping and density. Membership, dashboards, and project lenses are recalculated from canonical records whenever the Research workspace renders.
0smart collections
0saved views
0Sources
0Evidence
0Decisions
0Documented
0Projects
0Records
Dynamic view preview will appear here.
Definitions, not duplicate records.Smart collections and saved views are browser-local preferences. Their membership is recomputed from the v0.42 Advanced Retrieval corpus. No canonical research content is copied into this layer.
CROSS-PROJECT KNOWLEDGE
Reuse research across projects without copying the record.
Select a canonical research result above, choose a different project as the context that needs it, and record an explicit relationship. The source stays owned by its original project; Workspace stores only the pointer, target project, relationship, and your note.
0references
0target projects
0unresolved
No cross-project references yet.
Reference, do not duplicate.Cross-project knowledge is a browser-local ledger of canonical pointers. It never copies source content into the target project, silently changes project ownership, infers relationships, or mutates either project. Missing source/target records remain visibly unresolved.
RESEARCH TASKS / WORKFLOW STATE
Track what research needs next without changing the research itself.
Create explicit tasks around selected Integrated Knowledge records. Task state, priority, ownership labels, due dates, and history stay separate from the canonical record so “done” never silently changes a claim, source, citation, Notebook block, or Document.
0open
0in progress
0blocked
0unresolved
02 / WORKFLOW
Research task ledger
No research tasks yet. Select a research result first, then create a task only when a specific next action exists.
Workflow state is not research state.Research Tasks are browser-local canonical pointers. Completing, blocking, dismissing, importing, exporting, or deleting a task never edits the record it references. Workspace does not generate tasks automatically or infer that research is complete.
GROUNDED RESEARCH ASSISTANT II
Ask across Integrated Knowledge without expanding the scope behind your back.
Build an explicit multi-record grounding set from the research results on this page. Preparing a request freezes the selected records into an inspectable packet. Returned prose is accepted only when its citation markers resolve to that frozen set, and every substantive segment cites at least one selected record.
0draft sessions
0next-request scope
01 / SCOPE + QUESTION
Prepare a frozen grounding request
Select research above and add it to the grounding scope.
02 / PACKET
Provider-neutral grounded prompt
Select a prepared request to inspect its frozen grounding packet.
03 / RESPONSE + REVIEW
Citation-enforced draft
Grounding is a boundary, not a suggestion.Workspace does not call an AI provider automatically, expand the selected scope, invent citations, infer missing metadata, or write a canonical Document without an explicit reviewed-materialization action. Request packets preserve exactly what was supplied for later review.
KNOWLEDGE LIBRARY / PROJECT CONTINUITY
Carry research context into Workspace without creating a second library.
Stage saved searches, watchlists, research-queue items, source bundles, and private personal recommendations from the Knowledge Library. Every Library ID and origin remains visible. Nothing enters a Workspace project until you choose Add to project.
No Knowledge Library context is staged on this device.
One identity, two canonical systems.Authenticated Workspace and Library use the same WordPress account. Workspace does not copy the entire Library, read other users’ private recommendations, background-sync research, or mutate canonical Library records. Guest Workspace use remains first-class.
CITATION LIBRARY / REFERENCE MANAGEMENT
Manage reusable references without inventing metadata.
Normalize recorded bibliographic fields, detect likely duplicates, assign citation keys, preview common citation styles, and reuse references across projects. Missing authors, dates, publishers, identifiers, and DOI metadata remain missing until you enter them.
0references
0duplicate groups
LIBRARY
Reusable references
No references yet.
Recorded bibliography only.The Citation Library is browser-local Workspace data. It can normalize what you enter, but it does not query DOI services, scrape pages, infer missing metadata, automatically merge duplicates, or mutate Project records.
DOCUMENT / RESEARCH COMPOSITION
Compose structured research documents without copying canonical source records.
Build ordered sections, attach selected Workspace research and Citation Library references, preview the resulting document, and materialize it into a canonical Workspace Document only when you explicitly choose to do so.
0drafts
0inputs
01 / DOCUMENT
Structure and authorship
03 / INPUTS
Attach research and references
Select a section below before attaching inputs. Research attachments store canonical pointers, not copies of source content.
Composition remains reviewable until you materialize it.Drafts are browser-local. Canonical research is referenced, not copied. Citation metadata comes only from the Citation Library. Workspace never creates a Document automatically, rewrites a source record, or invents citations.
No research records yet. Begin with a project question or capture a source; this index fills from canonical local records as the work develops.
Retrieval over canonical records.Advanced Retrieval derives results from the Integrated Knowledge index at runtime. Saved searches are local browser preferences only. No server search index, semantic embeddings, automatic AI, inferred relationships, or canonical record mutation are introduced.
RESEARCH NOTEBOOK
Capture, connect, synthesize, and question research without losing provenance.
Keep working notes alongside captured sources, connect them explicitly, promote selected material into structured Workspace artifacts, and ask grounded questions against only the research you choose. Notebook originals remain in place.
0notebooks
0sections
0blocks
0promoted
0capture inbox
0collections
0links
0backlinked targets
0syntheses
0grounded questions
SOURCE CAPTURE / RESEARCH CLIPPING
Bring research into the notebook without losing where it came from.
Paste a source or excerpt manually, or review captures staged by compatible Sustainable Catalyst research surfaces. Workspace does not fetch the URL, scrape the page, infer citation facts, or save an incoming capture until you choose a destination.
INCOMING
Capture inbox
No incoming captures.
Choose or create a notebook.
02 / SECTIONS
Sections
03 / WORKING NOTES
Blocks
PORTABILITY / SYNC
Move notebooks without surrendering version history.
Export or import a notebook as an integrity-checked portable copy, create notebook-level restore points, or opt a signed-in notebook into explicit cross-device sync. Imports and restores always create new notebook copies.
Notebook remains local unless you explicitly export, back up, or enable sync.
No silent last-write-winsNotebook sync uses a server revision precondition. A stale device receives a conflict instead of overwriting a newer cloud notebook. Recovery preserves both copies.
REVIEW / PROVENANCE
Review notebook changes, reconcile selectively, and inspect lineage.
Compare the current notebook with one of its named restore points, choose individual changes to carry forward into a new notebook copy, reconstruct a notebook audit history from authoritative records, and inspect source lineage without hidden scoring.
01 / CHANGE REVIEW
Notebook diff
No notebook review generated yet.
02 / RECONCILE
Selective apply
03 / LINEAGE
Source lineage inspection
04 / AUDIT HISTORY
Derived notebook governance history
Notebook audit events will appear here.
Review is advisory; reconciliation is explicit.Change Review does not decide which state is correct. Selective reconciliation creates a separate notebook copy. Audit history and lineage are derived from existing notebook records; Workspace does not maintain a shadow provenance database or calculate a hidden change/confidence score.
COLLECTIONS / KNOWLEDGE LINKING
Connect notes, sources, notebooks, and structured Workspace objects explicitly.
Collections group research without copying it. Links create inspectable relationships between notebook material and existing Workspace objects; backlinks are derived from those explicit links.
04 / COLLECTIONS
Research collections
05 / LINKS & BACKLINKS
Explicit knowledge links
SYNTHESIS / CITATIONS
Build reviewable research structures from selected material.
Create outlines, citation packs, source matrices, evidence summaries, and research-synthesis drafts from notebook blocks and Workspace objects you explicitly select. Missing citation facts remain missing rather than being guessed.
No synthesis outputs yet.
GROUNDED NOTEBOOK ASSISTANCE
Ask against explicitly selected research—and require the answer to cite it.
Prepare a question using only selected Notebook blocks or Workspace objects. Grounding material is numbered locally. Returned or pasted answers must use those citation markers, and remain reviewable drafts until you explicitly accept or materialize them.
No grounded Notebook questions yet.
NOTEBOOK → WORKSPACE
Promotion lineage
Each derivative records the notebook block it came from. A block may be promoted more than once when different structured representations are useful.
No notebook material has been promoted into Workspace artifacts yet.
Notebook links are explicit working relationships, not inferred truth.Collections store references rather than duplicate research. Backlinks are derived only from links you create. Promotions remain explicit; every derivative is recorded in a visible promotion ledger and the notebook original remains preserved. Synthesis uses only material you explicitly select; citation facts are carried forward only when present. Grounded Notebook Assistance also uses only explicit selection, rejects answer citations outside that set, and keeps returned AI output as a reviewable draft. No AI submission, remote fetch, page scraping, semantic linking, citation guessing, source mutation, or upload runs automatically.
PROJECTS
Projects that preserve the reasoning.
Local project storage ready
No Workspace Projects yet.Create one to keep notes, objects, activity, and cross-product context together on this device.
PERSONAL KNOWLEDGE ENVIRONMENT
Find and reuse what you already know.
Search canonical Workspace Objects across projects, inspect provenance and internal references, discover transparent related-work signals, and organize reusable objects into local collections. The index is built in this browser from existing project data; Workspace does not upload it to a server.
0indexed objects
0projects represented
0collections
0distinct tags
01 / INDEX
Cross-project knowledge
No matching Workspace Objects yet. Objects remain project-owned; this index only makes them discoverable across the local Workspace.
03 / COLLECTIONS
Organize reusable objects without moving them.
Local index, canonical objectsPersonal Knowledge does not copy object bodies into a separate database. Search is derived from device-local projects; collections store only stable project/object references. Related-work suggestions use visible deterministic signals rather than hidden semantic scoring.
RESEARCH GRAPH & RELATIONSHIP EXPLORER
Trace how research moves from sources and notebook material through evidence, analysis, decisions, documents, citations, and synthesis.
The graph is derived at runtime from canonical Workspace records, Notebook links and backlinks, recorded provenance, promotions, synthesis selections, research evidence relationships, and Citation Library origins. Every edge remains inspectable.
0Nodes
0Relationships
0Projects
0Provenance sources
Choose two nodes to trace a path through recorded Workspace relationships.
01 / SEARCH
Graph nodes
02 / FOCUS
Relationship neighborhood
Inspectable graph, not inferred truthWorkspace builds this graph locally from explicit project containment, Notebook links/backlinks, recorded provenance, promotion records, synthesis selections, Citation Library origins, traceability, research evidence links, analysis inputs, decision inputs, and deterministic same-source matches. Path tracing and backlinks use only recorded graph edges. Library continuity appears as pointer nodes when explicit provenance exists. It does not use semantic embeddings, a server graph database, or hidden relationship inference.
WORKFLOW & ACTIVITY INTELLIGENCE
See what changed, what needs attention, and what comes next.
This view derives transparent signals from the work already stored on this device. It does not calculate a productivity score, monitor behavior outside Workspace, or mark work complete automatically.
Inspectable, not surveillantEvery signal states the project condition that produced it. Dismissal is user-controlled and stays on this device.
0active projects
0open next actions
0attention signals
0recent changes
01 / NEXT
Next actions you control
02 / ATTENTION
Explainable attention signals
03 / WORKFLOWS
Active workflow status
04 / TIMELINE
Recent local changes
No productivity scoreWorkspace summarizes explicit project state, workflow progress, unresolved review conditions, handoff status, and user-created next actions. It does not rank people, infer effort, measure time-on-page, or send activity telemetry to a server.
PROJECT VERSION HISTORY
Create deliberate restore points before important changes.
Restore points are named browser-local project snapshots with SHA-256 integrity fingerprints. They are separate from cloud sync and last-known-good Workspace recovery. Restoring never overwrites the current project; Workspace creates a new local copy instead.
Restore as copyThe original project remains untouched. Restore-point snapshots are bounded local copies, not an automatic server version history.
0restore points
0projects represented
0 KBsnapshot storage
Nonenewest point
01 / CAPTURE
Create a named restore point
Restore points are stored only in this browser.
02 / RESTORE POINTS
Local snapshots
03 / HISTORY
Recent version-history activity
Different recovery layers serve different purposes.Last-known-good recovery protects the entire browser Workspace from a damaged write. Account backup protects selected projects off-device. Sync compares local and cloud revisions. Restore points preserve named local project states for deliberate historical recovery.
PROJECT DIFF & CHANGE REVIEW
See what changed before you restore, sync, share, or promote.
Compare the current project with a named restore point—or compare two restore points from the same project. Workspace reports explicit added, removed, and modified records, including evidence, assumptions, decisions, and relationships. Nothing is applied automatically.
Review onlyChange Review is derived from existing project snapshots. It does not create a second project database, calculate a hidden change score, or modify either state being compared.
Choose a project and restore point to begin a change review.
0added
0removed
0modified
0relationship changes
No comparison generated yet.
No automatic reconciliationUse this review to inform a restore, sync, share, or institutional handoff. Workspace does not merge project states or infer which version is correct.
GUIDED RECONCILIATION & SELECTIVE APPLY
Carry forward only the changes you explicitly choose.
Start from a named restore point, compare it with the current project or another restore point, select individual changes, validate dependencies, and create a new reconciled project copy. Neither source state is edited.
New copy onlyWorkspace never mutates either comparison source, never auto-selects changes, and never performs a hidden merge. A reconciled result is always created as a separate local project.
Choose a project and base restore point to begin.
0available changes
0selected
0dependency blockers
0reconciled copies
01 / SELECT
Explicit changes
No comparison loaded yet.
02 / PREVIEW & DECISION
Reconciled copy preflight
Select one or more changes to build a preview.
03 / LEDGER
Recent reconciliations
No reconciled copies have been created yet.
04 / DECISION RECEIPTS
Auditable reconciliation provenance
No decision receipts have been created yet.
Selective apply is not an automatic merge.Workspace applies only checked records to a temporary candidate, validates dependencies, requires a decision-maker label and rationale, and creates a new project copy plus an integrity-fingerprinted decision receipt. Blocked plans cannot be created.
CHANGE GATES & SAFE ACTIONS
Require an explicit preflight before higher-risk actions.
Restore, conflict resolution, portable sharing, and institutional promotion now pass through a visible gate. Workspace shows the relevant change review, requires human acknowledgement, and records the local action decision before proceeding.
No hidden risk scoreGates explain what changed and what the action will do. They do not infer which state is correct, merge versions automatically, or rank project risk.
0gated actions
0proceeded
0cancelled
0changes reviewed
01 / POLICY
Actions protected by a gate
Restore as copyReview restore-point versus current state before creating the recovered copy.
Sync conflict resolutionCompare local and cloud states before choosing which becomes the working/sync head.
Portable sharingReview meaningful project changes and sharing scope before export.
Institutional promotionReview project changes and promotion scope before exporting to Catalyst Intelligence.
02 / LEDGER
Recent safe-action decisions
No gated actions have been recorded yet.
Human decision remains the control point.Change gates never apply, restore, merge, sync, share, or promote automatically. The action runs only after its preflight is shown and the required acknowledgement is explicitly checked.
GOVERNANCE MILESTONES & PROJECT LIFECYCLE
Declare where the work is—without letting the system decide for you.
Workspace derives a visible readiness checklist from the project’s evidence, analysis, decisions, review state, publication work, and governance records. The checklist informs a human lifecycle declaration; it never advances the project automatically.
Human-declared stateReadiness is evidence for judgment, not certification. A project may move forward or backward only after an explicit acknowledgement and rationale.
CURRENT STATEDraftNo milestone declared yet.
01 / READINESS
Supporting conditions for the selected milestone
Choose a project to inspect lifecycle readiness.
02 / DECLARE
Record a governance milestone
03 / HISTORY
Lifecycle declarations
No lifecycle milestones have been recorded yet.
No readiness score. No automatic advancement.Workspace records the conditions that were visible when a milestone was declared, including unmet conditions. The project owner can deliberately move backward when new evidence, review, or analysis warrants it.
PROJECT AUDIT TRAIL & GOVERNANCE LEDGER
See how consequential Workspace actions accumulated over time.
Audit Trail derives one chronological view from the authoritative histories already maintained by Workspace. It does not copy those events into a second shadow ledger.
Derived, not duplicatedRestore points, sync, Safe Actions, reconciliation receipts, collaboration, institutional handoffs, sharing, interoperability, and project activity remain authoritative in their original ledgers.
0events
0projects
0sources
Nonenewest event
No governance events are available in this view yet.
Audit events are reconstructed locally from existing Workspace ledgers.
No hidden governance score.The audit trail is chronological and source-labeled. Workspace does not score compliance, infer misconduct, rank people, or edit authoritative source events from this view.
IMPORT & INTEROPERABILITY
Move research between systems without losing where it came from.
Stage files locally, inspect the detected interchange profile and what Workspace will create, then commit into a project. v0.46 also exports structured Workspace JSON, Obsidian-ready Markdown, Notion-style CSV, Zotero-compatible CSL JSON, or a portable Workspace Project package.
Review before commitSupported inputs: JSON, CSV/TSV, Markdown, HTML, and plain text. Workspace recognizes common Obsidian front matter, Notion-style columns, CSL JSON, and Workspace interchange packages locally. Nothing is uploaded, enriched from the network, or treated as verified evidence merely because it was imported.
01 / STAGE
Inspect an external file
No file staged.
02 / EXPORT
Choose an interchange profile
Export canonical project material through an explicit format profile. Profiles are deterministic transforms of recorded Workspace data; they do not call external services or invent missing metadata.
Canonical remains canonicalEvery interchange export is a portable copy. Re-importing creates new draft objects or a new local Project copy rather than overwriting canonical Workspace records. Obsidian, Notion, and Zotero profiles are compatibility foundations—not live integrations.
03 / ACTIVITY
Recent interoperability activity
BACKWARD COMPATIBILITY
Know what Workspace will accept before you commit an import.
Project JSON is staged and classified locally. Supported historical schemas normalize only after explicit commit; newer future schemas are blocked rather than silently downgraded.
SHARED REVIEW ROOMS
Create controlled review spaces around a frozen project scope without surrendering canonical ownership.
v1.8.0 turns the existing collaboration, policy, and review-handoff foundation into explicit Shared Review Rooms. Rooms carry local role capabilities, deliberate invitations, immutable review snapshots, auditable review-state changes, and portable room exchange. They are controlled review records—not live co-editing, server ACLs, team cloud storage, or automatic canonical edits.
V1.8 / CONTROLLED COLLABORATION
Shared Review Rooms
Define who may review, freeze exactly what they should see, move the review through explicit states, and preserve a local audit trail. Existing Collaboration Architecture actors and policies remain the identity and ownership foundation.
0rooms
0active
0in review
0pending invites
01 / CREATE
Define a room and review scope
02 / ROOMS
Open controlled review spaces
03 / CONTROL
Invitations, snapshot, review state & audit trail
Review rooms are stored locally. No invitation has been sent externally.
Controlled review, not a shared tenantRoom roles and invitations are local governance records. Snapshot contents move only when you explicitly export a room package. Workspace does not create server accounts, send invitations, enforce organization permissions, live-edit canonical content, or apply accepted review proposals automatically.
V0.54 / CONTROLLED HANDOFF
Freeze only the research material a reviewer actually needs.
A prepared handoff stores an explicit object scope as a frozen package. Later project edits do not rewrite that package. Returned responses must match its fingerprint before Workspace will stage them.
0handoffs
0active
0staged
0unresolved
01 / DEFINE
Create a scoped handoff
02 / FREEZE & EXCHANGE
Prepare and reconcile the review package
Choose a handoff to prepare or review.
NO PACKAGE ASSESSEDPrepare a frozen package before importing a response.
No frozen review package prepared.
03 / REVIEWER RESPONSE
Prepare a package-matched response without touching the source Workspace.
No review package loaded.
No handoff action pending.
Staged review, not shared editingReview packages are explicit frozen copies of selected research objects. Responses must match the originating package fingerprint and are staged before import. Imported comments and proposals enter the collaboration ledger; no response automatically changes canonical research.
COLLABORATION ARCHITECTURE FOUNDATION · V0.53 COMPATIBILITY
INSTITUTIONAL GOVERNANCE · PROVENANCE · AUDIT
V1.9 / AUDIT STUDIO
Institutional Audit Studio
Assemble an explicit, reproducible governance dossier from authoritative Workspace ledgers without replacing them. Review provenance, decisions, review snapshots, reconciliation receipts, lifecycle records, citations, graph relationships, and institutional handoffs in one controlled audit package.
Auditability, not automatic complianceWorkspace exposes recorded evidence and lineage. It does not calculate a compliance score, infer regulatory status, certify an institution, submit evidence externally, or change canonical records automatically.
01 / SCOPE
Build an audit dossier
Scope remains explicit. Dossiers reference source ledgers and fingerprints rather than creating a new canonical governance database.
02 / ATTEST
Record human review
03 / REPRODUCIBLE PACKAGE
Inspect and export institutional audit evidence
No audit dossier staged.
Audit evidence remains local until you explicitly export it.
V0.53 / ARCHITECTURE
Collaboration contracts around canonical project ownership.
Actors and policies are local coordination records. Comments and proposals point to projects or objects by stable ID. Shareable-project contracts carry ownership, scope, and role declarations—not project content and not server permission grants.
0actors
0project policies
0open comments
0open proposals
01 / ACTORS
Local collaboration identities
02 / OWNERSHIP & GRANTS
Project collaboration policy
03 / COMMENTS
Canonical-target discussion
04 / PROPOSALS
Propose change without applying it
05 / SHAREABLE PROJECT CONTRACT
Export ownership, scope, and role declarations without project content.
No project policy selected.
Architecture, not enforcementRoles and capability grants describe intended responsibility in this local Workspace. They do not create server accounts, grant organization access, or protect a shared cloud tenant. Proposal acceptance records a review decision only; it never edits canonical project content.
COLLABORATION FOUNDATION · PORTABLE REVIEW COMPATIBILITY
0review sessions
0open threads
0contributors
0responses imported
01 / LOCAL IDENTITY
How you appear in review packages
This label is stored on this device and included only when you explicitly export a review package. It is not an account directory or permission grant.
02 / REQUEST
Start structured review
03 / SESSIONS
Review sessions
04 / REVIEW
Comments, suggestions & questions
05 / PORTABLE REVIEW
Move a review request or response deliberately.
No review package staged.
Collaboration foundation, not a shared tenantLegacy portable-review roles continue to describe responsibility inside review packages; they are not server-enforced permissions. Review packages retain source-revision fingerprints for freshness checks. Imported comments never edit the source project automatically. Workspace does not provide live co-editing; organization membership, shared cloud storage, audit-grade access control, and administrative governance remain outside this personal Workspace release.
INSTITUTIONAL VALIDATION
Validate the package before it leaves the personal Workspace.
Check frozen disclosure scope, recipient and purpose, source-revision freshness, promotion integrity, and institutional receipts. Attention states require human review; they are not readiness or quality scores.
Validation does not transfer authority.Passing these checks does not create organization access, accept a package into Catalyst Intelligence, or convert the source Workspace project into an institutional record.
Run validation or inspect a package/receipt file.
Institutional validation has not run yet.
INSTITUTIONAL RESEARCH PACKAGES
Freeze a deliberate research package for institutional handoff.
Select only the research that should travel. Workspace can include recorded provenance, related Citation Library references, Research Tasks, and Collaboration review context. The package becomes a frozen disclosure artifact; creating or exporting it does not alter the source project.
Explicit disclosureInstitutional packages contain selected copies for handoff. They are not public links, live mirrors, permission grants, or automatic Catalyst Intelligence imports.
01 / SCOPE
Define exactly what leaves Workspace.
Choose a project to define scope.
02 / PACKAGE LEDGER
Frozen institutional disclosure artifacts.
Open a frozen package to inspect its disclosure manifest.
Catalyst Intelligence promotion — compatibility pathThe v0.19 institutional promotion and receipt workflow remains available below. v0.57 packages are broader institutional research bundles and do not replace that explicit product-specific handoff.
INSTITUTIONAL HANDOFF
Promote mature work into governed institutional operations.
Prepare an explicit copy of selected Workspace material for Catalyst Intelligence while preserving the personal Workspace as an independent source record. Promotion is deliberate, inspectable, and does not convert the local project in place.
Copy into institutionThe source Workspace remains device-local and independently owned. Institutional governance begins only after the receiving system accepts the handoff.
0handoffs
0exported
0receipts
0accepted
01 / PREPARE
Define the institutional promotion
02 / HANDOFFS
Promotion ledger
03 / READINESS & EXPORT
Inspect before promotion
Prepare or open an institutional handoff to inspect scope and readiness.
04 / RECEIPT
Record institutional acceptance without rewriting the source project.
No institutional receipt staged.
Workspace does not become the institution.v0.25.0 preserves the governed handoff contract for Catalyst Intelligence while hardening the surrounding Workspace runtime. It does not create organization membership, server permissions, shared cloud storage, automatic ingestion, or an institutional tenant inside Workspace.
SCALE / PERFORMANCE
Know when a project is getting heavy before it becomes fragile.
Profile large-project pressure locally, inspect derived-index behavior, and keep rendering bounded. These signals are advisory only: Workspace will not delete, archive, compact, or migrate canonical research automatically.
Advisory, not destructivePerformance hardening changes derived caches and rendering windows, not Project 20.0 or Notebook 8.0 data.
0projects
0objects
0notebook blocks
0index entries
STORAGE0 KB
Browser quota estimate unavailable
DERIVED INDEX0 ms
0 hit / 0 miss
RENDER WINDOW120
Integrated Knowledge renders a bounded initial result window and exposes more only on request.
PERFORMANCE II / LONG SESSION
Watch runtime pressure without profiling your research.
v0.68 keeps a bounded, memory-only set of timing counters for route changes, full Workspace renders, derived-index work, cooperative yields, and supported browser long-task signals. Project content, query text, source URLs, and device identifiers are never included.
0 minsession age
0route changes
0full renders
0.0 msrender p95
0.0 msindex p95
0long tasks
0cooperative yields
Heap metric unavailableoptional heap signal
No advisory long-session signals
Bounded and localAt most 120 recent samples per metric stay in memory. There is no persistent profiling store, background submission, automatic cleanup of canonical research, or hidden productivity score.
No advisory scale signals
1.0.1 / FIELD STABILIZATION
Close the first post-GA production evidence loop.
Record representative field evidence for the live v1.0.1 deployment without collecting behavioral telemetry or inspecting project content. A valid v1.0.0 GA certificate remains the predecessor evidence boundary.
Evidence, not telemetryThis record is browser-local unless explicitly exported. Blocking defects keep the record on HOLD.HOLD
Post-GA field evidence is not yet closed.
v0.69 / PRODUCT RECOVERY & DISASTER SIMULATION
Prove the failure path before relying on it.
Run isolated in-memory recovery drills for corrupt state, interrupted writes, storage exhaustion, malformed imports, stale restore behavior, sync conflicts, missing references, and future-version mismatches. The simulator does not inject faults into canonical Workspace data.
CHECKING
Recovery drills have not run yet.
Recovery drill suite has not run yet.
Simulation is not destructive testing of your research.Faults run against isolated in-memory fixtures. Workspace does not corrupt live storage, force quota exhaustion, rewrite projects, auto-restore snapshots, auto-commit imports, resolve sync conflicts automatically, or contact a remote service during these drills.
SECURITY / PRIVACY / PORTABILITY
Know what Workspace stores, what it can disclose, and what deletion actually covers.
Audit browser-local Workspace data, review the same-origin threat model, export a complete local portability bundle, and verify browser-local deletion. This surface makes boundaries explicit rather than claiming encryption, authorization, or cloud deletion that Workspace does not provide.
Private by default, not magically encryptedBrowser localStorage is accessible within the browser/same-origin threat model. Integrity fingerprints are receipts—not encryption or authentication. Account/cloud data is a separate lifecycle boundary.
0local stores
0 KBlocal bytes
0disclosure stores
0recovery stores
01 / THREAT MODEL
Declared boundaries and non-claims
02 / FINDINGS
Current local audit findings
03 / DATA INVENTORY
Workspace-owned browser-local stores
04 / PORTABILITY
Complete browser-local export
The full portability bundle includes every current sc_workspace* browser-local key, including unclassified future keys. It may contain private research, recovery snapshots, identifiers, drafts, and disclosure artifacts.
05 / VERIFIED LOCAL DELETION
Delete Workspace browser-local data
This deletes Workspace-owned browser-local keys only. It does not delete account/cloud backups, WordPress records, previously exported files, or data already shared with another person/system.
Preview the deletion scope before enabling local deletion.
AUDIT II / RELEASE SECURITY
Re-audit the browser boundary without exporting the research.
Audit II inspects storage metadata, secure-context and embed state, script-readable cookie counts, and the release-time source gates that protect REST permissions and the current JavaScript runtime. Storage values, project content, URLs, queries, identities, referrer text, and cookie names/values stay out of the report.
Audit, not certificationThis is a bounded product security control. It is not a penetration test, cryptographic review, or claim that browser-local data is application-level encrypted.
0local stores
0session stores
0 KBWorkspace bytes
0unclassified stores
06 / BROWSER BOUNDARY
Runtime exposure metadata
07 / RELEASE GATES
Source controls enforced at packaging
08 / AUDIT II FINDINGS
Conditions that need review
Audit II has not run yet.
PUBLIC PRODUCT BETA II / READINESS
Test the complete Workspace, not just individual features.
Run a local product gate across persistence, integrity, recovery, focused-route isolation, performance diagnostics, security/privacy controls, and release identity. The gate produces explicit checks, never a hidden readiness score.
CHECKING
Running local beta checks…
Beta gate has not run yet.
Beta II boundaryChecks run locally and are advisory. Workspace does not send behavioral telemetry, submit diagnostics automatically, repair data automatically, mutate research, or convert checklist results into a productivity/readiness score.
PRODUCT HARDENING I / RELIABILITY
Recover the interface before it becomes a recovery problem.
Inspect browser capability, saved UI position, route isolation, and local recovery state. Workspace remembers only safe navigation state here; project and research data stay in their existing canonical stores.
CHECKING
Running local reliability checks…
Reliability check has not run yet.
Navigation recovery is not data recovery.Reset navigation state removes only Workspace UI-position keys. It does not delete projects, notebooks, citations, tasks, recovery snapshots, or other canonical research. Invalid or expired UI routes fall back to Start instead of trapping the application.
PRODUCT HARDENING II / PERSISTENCE INTEGRITY
Detect a bad save before recovery becomes guesswork.
Audit the canonical browser-local state, verified-save receipt, last-known-good snapshot, and write transaction journal. v0.62 adds integrity receipts and interrupted-write detection without changing Storage 35 or Project 20.0.
CHECKING
Running persistence integrity checks…
Persistence integrity audit has not run yet.
Integrity is not encryption or automatic repair.The checksum receipt detects persistence integrity drift and unexpected byte changes; it is not a security signature. Recovery candidate exports contain private Workspace content and remain manual-review artifacts. Workspace never overwrites canonical research merely because an integrity check reports attention.
v0.63 / CROSS-BROWSER & DEVICE COMPATIBILITY
Adapt to the browser without guessing from the browser name.
Inspect the runtime paths Workspace can actually use for persistence, navigation, file import/export, viewport sizing, touch input, and WordPress embedding. Feature detection controls fallbacks; browser-family labels are diagnostic only.
CHECKING
Running local browser capability checks…
Compatibility audit has not run yet.
Capability probes are not certification.v0.63 provides guarded fallbacks and automated capability fixtures, but it does not claim every physical browser/device combination has been manually certified. The exported target matrix is the field-QA checklist. Reports omit raw user-agent strings, device identifiers, project content, source URLs, query strings, and page fragments.
Audit support is not certification.Workspace targets WCAG 2.2 AA, but DOM/runtime checks cannot establish conformance on their own. v0.64 exports the remaining manual keyboard, screen-reader, contrast, forced-colors, zoom, reflow, reduced-motion, touch-target, and error-state checks. Reports contain no project content, source content, raw user agent, or device identifier and are never uploaded automatically.
FINAL AUDIT / ACCESSIBILITY + PERFORMANCE
Block critical regressions. Keep the remaining human verification visible.
Combine the existing keyboard/accessibility audit with bounded long-session performance evidence before Workspace enters the final beta-defect closure phase. Structural accessibility failures and critical performance regressions can block this automated gate; screen-reader, measured contrast, zoom/reflow, physical touch-device, and representative multi-hour validation remain human field work.
Automated gate, not certificationPassing this surface does not establish WCAG conformance or performance certification. It proves only that the automated release checks are below their blocking thresholds and that the remaining manual work is explicitly recorded.CHECKING
01 / ACCESSIBILITY GATE
Structural and runtime findings
02 / PERFORMANCE GATE
Session and interface budgets
03 / HUMAN FIELD VALIDATION
Checks automation cannot certify
Final audit has not run yet.
AUTOMATED DEFECT CLOSURE / PUBLIC BETA III
Close the automated backlog. Keep field validation visible.
Verify that the product journey, recovery simulations, security/privacy source gates, accessibility/performance final audit, WordPress metadata boundary, and current release identity remain coherent before Workspace enters the Release Candidate phase.
Closure is not field certificationAutomated blockers can be closed here. Production WordPress, assistive technology, physical touch/zoom/contrast, representative multi-hour use, two-device continuity, and real external handoffs remain explicit human field-validation work.CHECKING
01 / AUTOMATED GATE
Release blockers
02 / CLOSED DEFECT CLASSES
Protections that must not regress
03 / HUMAN FIELD VALIDATION
Explicitly unresolved until performed
Closure gate has not run yet.
RELEASE CANDIDATE I / FEATURE FREEZE
Freeze the product. Certify the release.
Verify that the Public Beta III closure baseline, recovery drills, security/privacy boundary, accessibility/performance gate, canonical schemas, and current release identity remain intact while the product enters the pre-1.0 certification phase.
Release Candidate is not production certificationFeature scope is frozen. Production WordPress, rollback rehearsal, assistive technology, touch/zoom/contrast, multi-hour use, two-device continuity, and real handoffs remain explicit human validation.CHECKING
01 / AUTOMATED GATE
Release Candidate blockers
02 / FEATURE FREEZE
Frozen product boundaries
03 / HUMAN FIELD CERTIFICATION
Required before production sign-off
Release Candidate gate has not run yet.
RELEASE CANDIDATE / PRODUCTION CERTIFICATION
Prove the package. Keep the live deployment honest.
Separate what the release archive can certify from what only the live WordPress deployment can prove: public-page health, REST identity, cache coherence, local-project preservation, and rollback behavior.
Package ready is not production certifiedLive field checks remain pending until you perform them on the deployed site. Workspace project storage is never a cache-remediation target.CHECKING
01 / PACKAGE GATE
Automated release evidence
02 / LIVE PRODUCTION
Explicit field certification
Production certification has not run yet.
LIVE PRODUCTION / RELEASE SIGN-OFF
Record the evidence. Sign off only what was actually tested.
Close the remaining pre-1.0 field-validation boundary with explicit human evidence. Every item stays pending until you attest that it was performed against the live deployment.
No automatic certificationWorkspace does not inspect project contents, infer pass/fail, purge caches, perform rollback, or sign on your behalf.PENDING
No live production evidence has been signed off.
PRE-1.0 / RELEASE READINESS
Close the evidence loop before calling Workspace ready for 1.0.
Use the signed v0.83.0 production certificate as prior evidence, verify the v0.84.0 release boundary, and make an explicit human readiness decision. This surface never promotes the plugin to 1.0 automatically.
Readiness is not releaseA READY dossier means the pre-1.0 evidence gate is complete. Publishing v1.0.0 remains a separate release action.HOLD
1.0 readiness has not been attested.
1.0 / GENERAL AVAILABILITY
Record the General Availability release boundary.
Use the valid v0.84.0 readiness dossier as predecessor evidence, verify the deployed v1.0.0 package and rollback path, and issue an explicit human GA release certificate.
GA is an explicit release recordWorkspace never infers readiness, publishes a release, purges caches, rolls back, or changes project data automatically.HOLD
General Availability has not been attested.
RELEASE CANDIDATE / WORDPRESS DEPLOYMENT
Verify the deployed release before blaming the workspace.
Check server package completeness, WordPress/runtime version coherence, current cumulative assets, registry retry state, and the rollback boundary without reading or changing browser-local project data.
Project storage is not a cacheA mixed-version deployment is repaired through release files and cache invalidation—not by clearing Workspace projects.CHECKING
01 / AUTOMATED COHERENCE
Current package and assets
02 / PRODUCTION FIELD CHECKS
Still requires a human
Deployment check has not run yet.
V1.10 / RESEARCH OPERATIONS
Research Operations: run recurring research work deliberately.
Plan saved-search refresh, source-update review, watchlist review, research-queue review, citation verification, provenance review, evidence refresh, and project maintenance. Workspace shows what is due or blocked, but nothing runs until you explicitly start it.
Schedules are declarations, not a daemon.
No background execution, automatic network request, canonical mutation, task creation, AI action, or telemetry occurs. External source freshness must be checked by the user.
PLAN
Operations queue
RUNS
Reviewable run results
Backward compatibility
The original Research Automation library below remains available. Legacy routines are imported only when you choose the import action; there is no automatic migration.
RESEARCH AUTOMATION FRAMEWORK
Schedule the reminder. Execute the research action yourself.
Create local routines for import review, source review, verification, synthesis refresh, and workflow follow-up. Cadence is declarative: Workspace never runs these jobs in the background or silently changes canonical research.
Manual execution onlyA routine becomes due locally, but nothing runs until you choose Run now or Run due routines. Every result is a draft receipt for human review.
01 / DEFINE
Create a reusable research routine
02 / RUN
Execute explicitly
03 / REVIEW
Automation run receipts
No automation has executed. Due schedules are local reminders only.
Automation prepares work; it does not decide or mutate.No routine performs background network requests, automatic imports, automatic AI calls, automatic task creation, source verification, synthesis replacement, or canonical data mutation. Imported routines never execute automatically.
V2.0 / CONNECTED KNOWLEDGE
Connected Knowledge Workspace
Use one explicit, provenance-aware context map across Workspace projects, research, Knowledge Library, Site Intelligence, Lab, Workbench, Decision Studio, review, audit, public knowledge, and developer extensions. Existing specialist products remain the canonical owners of their work.
01 / CONTEXT MAP
See the connected knowledge boundary
Build an ID-first view of the active local Workspace. Record bodies are not copied into the map.
No Connected Knowledge map has been prepared.
02 / CONNECTED SURFACES
Prepare a governed route
No context map prepared.
2.0 connects context; it does not seize ownership.v1 REST contracts remain available. Storage 35 / Project 20.0 / Export 20.0 remain compatible. There is no forced data migration, background federation, automatic specialist execution, automatic upload, automatic return commit, or hidden telemetry.
V1.13 / CONNECTED INTELLIGENCE
Connected Intelligence Workspace
Carry explicit project context into the Knowledge Library, Site Intelligence, Lab, Workbench, or Decision Studio through one provenance-preserving context envelope. Specialist products keep their own execution domains and canonical records.
01 / SPECIALIST CONTEXT
Prepare a governed handoff
Choose a specialist product to prepare explicit local context.
02 / CONTEXT RECEIPT
IDs, provenance, and routing remain visible
No connected context prepared.
V1.14 / PUBLIC RESEARCH PACKAGES
Public Research Packages & Portable Knowledge Objects
Create a deliberate public projection from selected Workspace records. Private project material stays private unless you explicitly select it, disclose fields, choose a license, and confirm release.
Private by defaultRelease creates a new portable projection. It does not alter the canonical Workspace record and does not upload or publish anything to a server.
01 / SELECT & DISCLOSE
Build a private draft package
Nothing has been selected or published.
02 / MANIFEST & PROVENANCE
Review exactly what will travel
No public research package prepared.
Publication is a projection, not a privacy-state toggle.Portable objects record source IDs, included and excluded fields, provenance, license, and SHA-256 fingerprints. No automatic upload, network request, AI action, telemetry, or canonical mutation occurs.
V1.12 / SCALE & RELIABILITY
Large Workspace & Institutional Scale Hardening
Assess the current local Workspace against explicit scale envelopes for projects, objects, notebook blocks, search entries, graph volume, citations, and storage pressure. Workspace recommends bounded rendering, chunked indexing, bounded graph expansion, sharded exports, and recovery-first handling without deleting, compacting, archiving, migrating, uploading, or offloading canonical work.
01 / ENVELOPE
Deterministic scale assessment
Attention and critical thresholds are visible contract values—not hidden health scores.
No scale assessment has been run.
02 / DEGRADATION PLAN
Bound work before pressure becomes corruption
Run the scale assessment to review the deterministic handling plan.
V1.15 / PRODUCT MATURITY
Product Maturity & 2.0 Candidate
Close the 1.x maturity line with explicit evidence across UX, accessibility, performance, compatibility, API stability, recovery, portability, governance, privacy, deployment, documentation, and field evidence.
No hidden scoreEach dimension is Ready, Attention, or Blocked. A 2.0 candidate designation is human-controlled and does not create v2 schemas, migrate data, or promote Workspace automatically.
No maturity dossier has been built.
Evidence remains local until you explicitly export a maturity package.
V1.11 / DEVELOPER API & EXTENSIONS
Developer API & Extensions: build against stable Workspace contracts without bypassing Workspace governance.
The Developer API publishes versioned schemas, a browser-local SDK, extension manifests, and explicit capability grants for Workspace objects, search, Library continuity, Knowledge Graph, Lab and specialist handoffs, Review Rooms, Audit Studio, and Research Operations.
Read-only by defaultExtension manifests declare requested capabilities. Grants are explicit portable governance records—not credentials—and no extension receives arbitrary code execution, remote loading, or hidden canonical mutation rights.
01 / CONTRACTS
Stable versioned extension surface
/wp-json/sc-workspace/v1/developer-api-contract
Breaking changes require a new major contract. Additive v1 changes must preserve existing fields and semantics.
No extension manifest has been exported.
02 / CAPABILITIES
Explicit grants, bounded access
Extension contracts are not an execution sandbox.v1.11.0 does not install extensions, load remote JavaScript, expose mutation REST endpoints, store secrets in manifests, place tokens in URLs, perform background network requests, or let integrations bypass project ownership, provenance, privacy, review, or audit controls.
\n\n
API, EMBED & INTEGRATION HARDENING
Expose a deliberate read-only projection through a bounded integration boundary.
Canonical research remains private and browser-local by default. Create an explicit static projection when a particular record should travel through an API envelope or embed. Durable references identify records but never grant access.
Private by defaultNo live server project API exists. Export and embed paths fail closed when integrity, payload size, or trusted-renderer checks do not pass.
01 / SELECT & DISCLOSE
Create a read-only projection
Creating a projection does not upload it. It creates a browser-local disclosure package that can then be explicitly exported or embedded.
02 / REFERENCE & API
Stable reference and static JSON envelope
DURABLE REFERENCENo projection selected.
No API envelope selected.
03 / STATIC EMBED
Preview and copy a self-contained read-only embed.
Create or select a projection to preview its read-only embed.
No projection has been disclosed.
04 / INTEGRATION SAFETY
Verify the boundary before the projection travels.
Select a projection to run integration safety checks.
Checks are local and diagnostic. They verify the projection fingerprint, bounded payload size, static read-only governance, and configured HTTPS renderer origin. They do not authenticate the recipient or turn a fingerprint into a signature.
Identifiers are not credentials.A scw:// durable reference is safe to use as a stable identifier only. It does not prove identity, confer permission, expose private local records, or act as an access token. Static fingerprints detect package changes; they are not signatures or authorization. Static embeds perform no credentialed fetch, postMessage bridge, or remote canonical mutation.
SHARE & PORTABLE PROJECTS
Move a complete project without turning Workspace into a cloud service.
Create a deliberate portable copy for another person or device, verify package integrity on import, or export a static review copy that can be read without Workspace.
Portable copy, not syncWorkspace does not create public share links, upload projects, or establish live collaboration. Device identity, account/session metadata, handoff state, and recent-tool history are excluded.
01 / PACKAGE
Create a portable project
Privacy-minimized by defaultPortable JSON preserves the reasoning structures needed to continue the project. Operational browser metadata is stripped. Activity and AI review history are opt-in because they may contain context that is unnecessary for sharing.
02 / RECEIVE
Import a portable project as a copy
No portable project staged.
No overwriteImported packages receive a new local project ID and are rebound to this device. Their internal canonical object relationships are preserved, but they cannot replace an existing local project automatically.
03 / ACTIVITY
Recent portable sharing activity
ACTIVE PROJECT
Project
Saved on this device
PROJECT ID
TEMPLATES & GUIDED WORKFLOWS
Add structure when the work benefits from it.
Start from a visible method for research, evidence review, analysis, decisions, systems mapping, or publication preparation. Templates guide the sequence; they do not create hidden findings, complete steps automatically, or prevent blank-project work.
0workflow runs
0in progress
0steps complete
REUSABLE RESEARCH TEMPLATES
Scaffold a method without copying the research.
Use built-in protocols or explicitly saved custom structures to add a guided workflow, a Notebook section scaffold, and optional empty starter objects. Templates never contain project notes, Notebook contents, evidence, findings, citations, or completion states.
01 / TEMPLATES
Choose a method, not a locked tier.
02 / RUNS
Keep more than one method in the same project.
ACTIVE WORKFLOWNo active guided workflow selected.
03 / STEPS
Progress remains explicit and human-controlled.
Open a step to move into the relevant Workspace mode. Mark completion yourself; Workspace never interprets activity as approval or completion.
RESEARCH WORKSPACE
From question to evidence-backed claim.
Frame inquiry, capture sources, manage a reading queue, extract evidence, and test claims while retaining stable links to Workspace Objects.
ACTIVE QUESTIONNo active research question selected.
02 / SOURCES
Capture & reading queue
03 / EVIDENCE
Extract evidence
04 / CLAIMS
Claims & evidence
ANALYSIS WORKSPACE
From evidence to structured analytical finding.
Frame analytical questions, register datasets and variables, surface assumptions, record methods and comparisons, and connect findings back to Workspace evidence and analysis objects.
ACTIVE QUESTIONNo active analysis question selected.
02 / DATA
Datasets & variables
03 / METHOD
Assumptions & methods
04 / INTERPRETATION
Comparisons & findings
DECISION WORKSPACE
From analysis to accountable decision.
Frame decisions, compare options against explicit criteria, record assessments and risks, and preserve the selected course, rationale, confidence, and supporting evidence as a durable Workspace Decision object.
Make relationships visible without flattening the reasoning.
Create project boards that connect questions, claims, evidence, data, analyses, decisions, systems, stakeholders, and ideas. Canvas nodes can reference existing Workspace Objects while relationships and frames preserve how the pieces fit together.
Assess evidence, connect object lineage, fingerprint important artifacts, and record enough analytical context for another person—or your future self—to understand what produced a result.
0assessed evidence
0lineage links
0reproduction records
0verified records
01 / EVIDENCE QUALITY
Assess the evidence explicitly.
The four ratings are a transparent working heuristic, not an automated truth score.
02 / LINEAGE
Connect how artifacts relate.
03 / REPRODUCIBILITY
Record what would be needed to reproduce an analysis.
RESPONSIBLE AI ASSISTANCE
Ask for help without hiding the basis of the work.
Prepare grounded AI requests from selected Workspace Objects, review responses locally, and explicitly accept useful material as a draft Document. Workspace does not automatically send project content to a model, approve decisions, publish outputs, or overwrite evidence.
HUMAN CONTROLLEDPrepare → review → accept or reject
0requests
0grounding refs
0responses
0accepted drafts
01 / PREPARE
Ground an assistance request.
02 / REQUESTS
Keep assistance sessions reviewable.
ACTIVE REQUESTNo active AI assistance request.
03 / GROUNDING
Make the source basis visible.
Preparing a request is local. No selected object content is sent automatically. A compatible same-origin Research Librarian adapter can read the prepared request only after this explicit user action. If no adapter is active, use Copy or Export instead.
04 / REVIEW
Treat AI output as a draft, not evidence.
AI does not become evidence by acceptance.Accepted output becomes a working Document object tagged ai-assisted and human-accepted. Any selected citation objects remain separate canonical Sources/Evidence and are linked through visible provenance lineage.
BRIEFING & PUBLICATION STUDIO
Turn connected project work into something another person can use.
Compose briefings, memos, reports, articles, and publication drafts from existing Workspace Objects while preserving the basis of the work. Workspace exports portable drafts; it does not publish directly to a CMS.
0drafts
0ready
0object references
0document outputs
01 / DRAFTS
Create a communication artifact.
02 / BASIS
Choose the objects this draft is based on.
ACTIVE DRAFTNo active draft selected.
03 / STRUCTURE
Build the narrative without hiding the underlying work.
04 / OUTPUT
Create a reusable document or export a portable draft.
Exports include the authored draft and traceable object references. Workspace does not automatically publish or write to WordPress, Publications, or the Knowledge Library.
WORKSPACE OBJECTS
Reusable work inside this project.
Sources, evidence, datasets, analyses, decisions, documents, and exports share one stable local object contract.
0 / 250 objects
No Workspace Objects yet.Create a typed object to start turning project work into reusable artifacts.
Carry selected scientific context into Lab and return traceable results.
Select the exact Workspace objects Lab should receive. Exporting a scientific context package is explicit; opening Lab carries only stable IDs in the URL. Returned results must match the originating project and handoff before Workspace materializes them.
Only explicitly selected source, evidence, dataset, analysis, document, and export objects are copied into the portable context package. Nothing is uploaded automatically.
Execution stays in LabWorkspace preserves project identity, selected object IDs, provenance, scientific metadata, and deterministic derived-from traceability. It does not run models, infer scientific relationships, or commit unmatched returns.
WORKBENCH / DECISION STUDIO ROUND TRIP
Move bounded project context into specialized tools and bring governed outputs back.
Choose Workbench for calculation, simulation, optimization, engineering analysis, transformation, or sensitivity work. Choose Decision Studio for decision packets, scenarios, tradeoffs, option assessment, risk review, or decision briefs. Workspace preserves the project and provenance boundary; the specialist tool performs the work.
Only explicitly selected compatible Workspace objects are copied into the portable context package. Opening the specialist tool carries stable IDs only; no project content is uploaded automatically.
Specialized execution stays specializedWorkspace records the handoff, selected context IDs, destination, workflow, provenance, and deterministic derived-from traceability. It does not run Workbench calculations or Decision Studio analysis itself, and it rejects returns that do not match the originating project, handoff, and destination.
CROSS-PRODUCT HANDOFFS
Connections & returns
Review return activity or import a structured return package when you need it. The underlying handoff IDs and privacy checks remain intact.
Context, not contentOutbound URLs carry only stable IDs, destination intent, and a return signal. Structured returned content is accepted locally through the return inbox and becomes ordinary Workspace Objects with tool provenance.
ADAPTER DIAGNOSTICSWorkspace now normalizes canonical returns from Research Librarian, Knowledge Library, Site Intelligence, Workbench, Analytics R, Decision Studio, Catalyst Canvas, Catalyst Data, and Lab. Automatic returns must match the locally recorded project, handoff ID, and destination.
No handoffs recorded for this project yet. Open a connected tool below to create the first handoff.
CONNECTED TOOLS
Open a specialized Sustainable Catalyst tool.
The active project context stays available when supported tools open and return work.
