Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

PointSav Digital Systems

Diode standard

← All revisions

8cbac063 · PointSav Digital Systems ·

editorial(security): re-verify diode-standard (Track-B) — asymmetric/ingress diode self-descriptions confirmed still live in tool-egress-pull + master-harvester-rs, placeholder crate still empty; dropped 2 repo-path/methodology citations per register-documentation.yaml

View the full record as of this revision →

@@ -11,7 +11,7 @@ status: active
audience: vendor-public
bcsc_class: forward-looking
language_protocol: PROSE-TOPIC
last_edited: 2026-08-03
last_edited: 2026-08-22
editor: pointsav-engineering
short_description: "The Diode Standard is the design rule that command and data flow in one direction only, from authority to subject. Several real mechanisms follow it; no component enforces it as a named standard."
paired_with: diode-standard.es.md
@@ -87,8 +87,8 @@ directionality as a rule.

### Directional code promotion

The strongest enforcement in the platform is over source code rather than runtime data. Promotion
(`bin/promote.sh`) runs in one direction only — from staging mirrors, to the canonical repository,
The strongest enforcement in the platform is over source code rather than runtime data. The
promotion step runs in one direction only — from staging mirrors, to the canonical repository,
to local service mirrors — and the script actively refuses the reverse case: it permits only
fast-forward pushes or explicit commit-by-commit replays onto the canonical branch, blocks true
history divergence, blocks mass deletions above a threshold, blocks patterns that would silently
@@ -101,11 +101,10 @@ runtime command path the standard describes.

Earlier descriptions of this standard named a specific enforcing component — a small,
hot-pluggable link service, absent by default and installable by the operator, that would be the
only code translating authority commands into subject-executable operations. Direct search of the
canonical source tree confirms that no package of that name, under either of the two names
previously used, exists anywhere. A corpus-wide search for both strings, and for "Diode" or
"DiodeStandard" in Rust source, returns nothing outside documentation about this article's own
subject.
only code translating authority commands into subject-executable operations. No package under
either of the two names previously used exists anywhere in the platform's source, and neither
"Diode" nor "DiodeStandard" appears anywhere in the Rust source outside documentation about this
article's own subject.

The one package with a similar-sounding name is a seven-line placeholder whose single function
returns a scaffold-verification string and whose dependency list is empty. It contains no
Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. 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. The full trademark notice appears in the footer of every page on this site.

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 →