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

Revision as of · 0c44634d

Historical revision — this record as it stood on 22 August 2026, not the current version. View the current record →

Archetypes and chart of accounts

The Chart of Accounts and the eleven archetypes are two reference taxonomies service-content — entity extraction and knowledge-graph host maintains as CSV files and loads into the knowledge graph as static entities. Together they give every classified document or entity two independent labels: where it sits in an institutional structure, and what functional role it plays. A reader who only needs the vocabulary can stop after the two tables below; a reader who wants to see how the platform actually uses them should continue to the Verification Surveyor section.

Two reference tables, two dimensions

Table Real shape What it captures
Chart of Accounts reference_number, category, type, gravity_keywords — a flat, two-level list, not a deep hierarchy Structural position: which institutional category (Personal, Compliance, Real Estate, Construction, and others) and which specific type within it
Eleven Archetypes id, name, signature, healing_trigger, gravity_keywords — one row per archetype Functional role: what a person or entity does, independent of job title

A small sample of the real Chart of Accounts:

Reference Category Type
1001 Personal Director
2001 Compliance Counsel
2002 Compliance Accounting
3003 Real Estate Office Leasing

The Chart is flat by design — a category and a type, nothing deeper. There is no separate "Domain" or "Sub-Domain" layer; the type field carries that level of specificity directly.

The eleven archetypes

Each archetype row carries a name and a short signature. It also carries a "healing trigger" — the failure mode the archetype is defined against:

Archetype Signature Healing trigger
The Executive Strategic Direction Stagnation
The Guardian Risk & Compliance Breach
The Fiduciary Resource Integrity Leakage
The Architect System Design Complexity
The Engineer Technical Execution Friction
The Artisan Creative Precision Homogeneity
The Constructor Physical Realization Structural Gap
The Catalyst Growth & Momentum Inertia
The Envoy External Synergy Friction
The Steward Asset Preservation Degradation
The Sage Knowledge & Vision Ignorance

Both tables also carry a gravity_keywords column — a pipe-separated list of terms associated with the row (a Guardian's keywords include "compliance," "counsel," "audit," "legal"). This column exists in the data today as reference vocabulary; no classification code currently matches incoming text against it automatically.

How the taxonomy reaches the knowledge graph

service-content — entity extraction and knowledge-graph host exposes a small admin API that reads each CSV file and loads its rows into the graph as static entities. The eleven archetype rows load as classification: "archetype", the Chart of Accounts rows as classification: "coa-profile", both tagged with a dedicated __taxonomy__ module so they're distinguishable from entities extracted from real documents. Reloading either file replaces the prior set of rows rather than appending to it.

Where the archetype label is actually applied

The archetype taxonomy's one confirmed point of use today is the Verification Surveyor tool. When an operator manually verifies an extracted entity's identity, the tool prompts them to pick one of the eleven archetypes from the ontology file and records that choice as a claim on the entity, alongside the verification timestamp and source URL. This is a human decision made once per entity during review — not an automated inference, and not a mechanism that evaluates or scores a person's ongoing behaviour against their archetype. The Chart of Accounts categories are not part of this workflow; only the archetype selection is.

See also

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 →