WGS References
This folder preserves the planning lineage behind the Aptlantis governance system. These files are not active standards unless a standard suite explicitly cites them as authoritative — see the Reference Index for the rule governing their use.
They matter because they carry tone, intent, and design memory from before WGS was formalized. The standards themselves should remain practical, recoverable, and agent-friendly, not ceremonial; these documents are where the why behind that posture was worked out.
Workspace Governance Planning Documents
| Document | Role | Format(s) |
|---|---|---|
| WGS.txt | Earlier WGS planning draft — an earlier, more discursive pass at the same territory the current Workspace Governance Standard.md now covers formally. | txt |
| Workspace Governance Standard (WGS) — The Architectural Constitution of the Aptlantis Ecosystem | Rendered architectural WGS reference; a polished writeup of the constitutional framing that predates the current spec. | |
| Operationalizing the Aptlantis Ecosystem: The Future of Workspace Governance | Workspace governance strategy reference — the plain-text source of the operationalization essay. | txt |
| Operationalizing the Aptlantis Ecosystem - The Future of Workspace Governance | Same essay, rendered and editable copies. | pdf, docx |
| Operationalizing AI Agent Effectiveness: A Governance-Led Framework for the Aptlantis Workspace | Agent governance reference — early thinking on what became the Agent Startup Procedure and agent-first governance rules. | txt |
| The Aptlantis Governance Framework: A Comprehensive Overview of Ecosystem Standards | Ecosystem overview reference — an early survey of the full standards suite, predating the current Standards Backlog and Documentation Suite Roadmap. | txt |
These files are long-form planning prose (multiple thousand words apiece) rather than short reference notes, so they are linked as static downloads instead of being inlined into a doc page.
Conversation Lineage
The long-form planning conversations live under Conversations. Use them when a standard feels mechanically correct but philosophically thin — they carry the back-and-forth reasoning that produced the current rules.
The primary lineage file is the ChatGPT standards-development transcript, which is substantially longer (over 7,500 lines) than every other reference document and is treated as the anchor conversation for how the whole SFDS/WGS split came about.
Use Rule
Reference files may inform tone and planning, but active implementation should follow the standard suites:
- WGS for workspace structure.
- SFDS for standard authoring.
- PPS for project proposals.
- DRS, CTS, SIS, WDS, and DDS for project classes.
:::note Cross-references PPS, DRS, CTS, SIS, WDS, and DDS are not yet built as documentation slices in this site (see the Standards Backlog). These references are left as plain text pending those standards' own documentation passes. :::