Skip to content

Seed taxonomy as SMB bootstrap

← All revisions

a8a019c4 · PointSav Digital Systems ·

enrich wikilinks: documentation substrate body (EN+ES) batch 4 of 4

View the full record as of this revision →

@@ -14,7 +14,7 @@ cites: []
paired_with: seed-taxonomy-as-smb-bootstrap.es.md
---

Every tenant deployment begins with a **seed taxonomy**: a compact, hand-tunable four-part structure that forms the initial scaffold of the per-tenant knowledge graph. The four parts are Archetypes, Chart of Accounts, Domains, and Themes. Each entity carries gravity keywords — explainable keyword anchors that drive classification of incoming content.
Every tenant deployment begins with a **seed taxonomy**: a compact, hand-tunable four-part structure that forms the initial scaffold of the per-tenant [[knowledge-graph-grounded-apprenticeship|knowledge graph]]. The four parts are Archetypes, Chart of Accounts, Domains, and Themes. Each entity carries gravity keywords — explainable keyword anchors that drive [[service-content|classification of incoming content]].

## The four parts

@@ -28,7 +28,7 @@ Every tenant deployment begins with a **seed taxonomy**: a compact, hand-tunable

## The gravity_keywords mechanism

Classification of new content into the taxonomy uses keyword matching rather than embedding similarity. When a document arrives, the extraction service counts keyword matches against each Archetype, Chart of Accounts profile, Domain, and Theme entity. The entity with the highest match count is the proposed classification.
Classification of new content into the taxonomy uses keyword matching rather than embedding similarity. When a document arrives, the [[service-extraction|extraction service]] counts keyword matches against each Archetype, Chart of Accounts profile, Domain, and Theme entity. The entity with the highest match count is the proposed classification.

This approach is deliberate. Keyword-based classification is explainable: "this document was classified as Real Estate because the terms Leasing, Office, and Industrial matched" is a statement an operator can read and verify. An embedding similarity score is not. Keyword classification is auditable — the classification path is reproducible across model versions, which matters for regulatory record-keeping. And it is hand-tunable: an operator who sees a misclassification edits the gravity keywords list. Retraining an embedding model is not a practical operation for a small business.

@@ -36,7 +36,7 @@ Embedding similarity is provided at a separate layer to augment keyword classifi

## Provisioning a new tenant

When a new tenant is provisioned, the operator selects a Vertical Seed Pack (see [[vertical-seed-packs-marketplace]]) appropriate to their industry. The service imports the pack's JSON files into the per-tenant graph. The operator then customizes the result — adding, editing, or removing entities — using the TUI. A typical small business is intended to complete the review and customization in approximately 30 minutes.
When a new tenant is provisioned, the operator selects a Vertical Seed Pack (see [[vertical-seed-packs-marketplace]]) appropriate to their industry. The [[service-content|service]] imports the pack's JSON files into the per-tenant graph. The operator then customizes the result — adding, editing, or removing entities — using the [[tui-corpus-producer|TUI]]. A typical small business is intended to complete the review and customization in approximately 30 minutes.

## Structural difference from enterprise ontology approaches

@@ -46,7 +46,7 @@ The platform's seed taxonomy optimizes for actionability for one specific custom

## Relationship to the knowledge graph

The seeded taxonomy becomes the initial structure of the per-tenant knowledge graph in `service-content`. Every Archetype, Chart of Accounts profile, Domain, and Theme entity is a graph node. As the deployment operates, new entities discovered during inference (with accepted verdicts) are added to the graph, growing the taxonomy organically from actual use.
The seeded taxonomy becomes the initial structure of the per-tenant knowledge graph in [[service-content]]. Every Archetype, Chart of Accounts profile, Domain, and Theme entity is a graph node. As the deployment operates, new entities discovered during inference (with accepted verdicts from the [[compounding-doorman|Doorman]]) are added to the graph, growing the taxonomy organically from actual use.

The [[knowledge-graph-grounded-apprenticeship]] pattern depends on this seeded graph: the graph provides the grounding context for every subsequent inference request.

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 →