Skip to content
PointSav Digital Systems

Last updated · 092d3c7f · Español

Six-tier sovereignty matrix

The PointSav monorepo organises every directory by purpose, not by programming language or compile format. Each directory at the repository root belongs to one of six tiers — app-, asset-, moonshot-, os-, service-, or system- — identified by a fixed prefix. A contributor reading the prefix knows immediately what layer a directory operates at without opening a file. This article covers the six tiers, the decision rule for classifying new directories, the kebab-case constraint that makes the taxonomy portable across operating systems and container registries, and the legacy names the taxonomy supersedes.

The six tiers

Every directory at the monorepo root falls into one of the following tiers:

Tier Prefix Purpose Example components
1 — Application app- User-facing surfaces — the personality cartridges that define how a job looks and feels app-console-input, app-mediakit-marketing, app-orchestration-command
2 — Asset asset- Non-code resources — fonts, icons, 3D models, design tokens, brand assets asset-brand-pointsav, asset-brand-wcp
3 — Moonshot moonshot- Research and development experiments not yet promoted to production moonshot-gpu
4 — OS os- Operating-system compositions — the runtime containers that load other components os-console, os-totebox, os-orchestration
5 — Service service- Background business-logic daemons service-slm, service-content, service-email, service-people
6 — System system- Foundational technology — drivers, networking, foundation utilities system-foundation, system-driver-network, system-audit

The word "library" is explicitly retired as a category label. It describes how code is compiled, not what it does.

The rule of purpose

A new directory is classified by its purpose, not its format. The decision is short:

Question Tier
Does it talk to the computer — date parsing, networking, math, filesystem? system-*
Does it talk to the user's life — contacts, email, photos, accounting? service-*
Does it define the look and feel for a specific job? app-*
Is it a non-code resource — a font, an icon, a design token? asset-*
Is it speculative research not yet committed to production? moonshot-*
Does it compose other components into a runtime container? os-*

Why the prefix discipline scales

Three structural advantages emerge from the taxonomy:

Advantage Effect
Discoverability A new contributor reading a directory name knows immediately what layer it operates at without opening a file
Dependency hygiene app-* may depend on service-* and system-*; service-* may depend on system-*; system-* has no upward dependencies — cyclic dependencies are mechanically impossible
Composition over inheritance An operating system is an os-* composition that loads app-* cartridges and connects to service-* daemons; the OS contains no feature-specific code

This is the filesystem-level expression of composition over inheritance: the OS is a generic engine; the application is the personality.

Strict kebab-case

All six tiers use lowercase ASCII with hyphens. Capital letters are not permitted. The constraint holds across Docker registries, case-sensitive Linux filesystems, case-insensitive macOS filesystems, and DNS subdomains.

Form Status Reason
os-totebox Canonical Lowercase kebab-case
Totebox-OS Not permitted Mixed case creates phantom drift across operating systems
Totebox_OS Not permitted Underscores are not standard in repository or container names
toteboxos Not permitted Loses readability without a delimiter

Uppercase is preserved only for a small set of root-level operational files — README, LICENSE, CLAUDE.md, AGENT.md — where the convention predates the kebab-case rule.

Name supersession

The taxonomy took several generations to settle. Earlier names appear throughout the source archive and are normalised when content is migrated:

Earlier name Current canonical
lib-pointsav-* package-* (shared libraries)
software-pdfs, software-wordprocessing app-workplace-pdfs, app-workplace-wordprocessor
console-people, node-console-people app-console-people
sys-marketing, sys-knowledge, sys-distro app-mediakit-marketing, app-mediakit-knowledge, app-mediakit-distribution
fleet-infrastructure-*, gateway-interface-*, route-network-admin app-infrastructure-onprem / -leased / -cloud, app-orchestration-command, app-network-admin

See also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →