Audit portable-workspace planning language for the independent HotMem identity

[valiantone]

Context

HotMem’s public issue tracker currently contains planning language that is broader than the neutral portable-workspace foundation described here. Issue #83 establishes an independent open-source identity and a sanitized-content boundary. The foundation issues must be publishable without exposing private strategic rationale or introducing claims that the project has shipped capabilities it does not yet have.

What needs to be done

• Approve a public vocabulary centered on portable workspaces, runtime/mount identity, snapshot fidelity, hydration, and replay safety.
• Define an internal-only vocabulary boundary for private product strategy, ecosystem relationships, market/moat framing, customer context, and internal sequencing.
• Audit issue titles and bodies, labels and descriptions, milestones, project fields, pull-request templates, roadmaps, release notes, badges, and linked public documentation.
• Propose reviewed edits for Define HotMem interchange and company-brain clone package v1 #67, Ship verified portable company-brain dump and hydrate workflow #69, affected labels, and any other confirmed leak; coordinate with Establish an independent open-source identity for HotMem #83 rather than duplicating its broader identity migration.
• Preserve approved legal or historical attribution as explicit exceptions.
• Add a lightweight pre-publication checklist for issues, pull requests, docs, and release notes.

Acceptance criteria

• The public/internal terminology map is reviewed and approved.
• The audit covers every listed release surface and records evidence for each finding.
• Proposed public wording contains no unintended private strategic, ecosystem, customer, market, or internal-sequencing material.
• Approved edits preserve intentional legal or historical attribution and link Establish an independent open-source identity for HotMem #83 where appropriate.
• The checklist is usable for issues, pull requests, documentation, and release notes.
• No public edit is made from this issue without final review of the exact diff.

Constraints and non-goals

This issue does not rename the repository or package, transfer organizations, change legal ownership or licensing, complete all of #83, or publish private Atlas material. Public-neutral wording must not conceal technical limitations or provenance.