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 · 0a5e6d5e

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

Export structured data from the platform

Prerequisites

  • Access to the DataGraph MCP tools, for entity exports
  • Read access to the relevant media-knowledge-* git repository, for wiki exports
  • Network access to service-fs and your module identifier, for ledger exports
  • A device paired to the workspace (see Pair a new device)

Purpose

Pick the right export path for what you're actually trying to get out of the platform — entity records, article content, or audit-grade ledger history each have a genuinely different real mechanism.

Procedure

Path 1: Entity data from the DataGraph

Use this for structured records about a person, organization, project, or service.

  1. Call query_datagraph to identify the entity, then get_entity_context on its identifier to retrieve the full profile — see Query the DataGraph for the exact tool signatures.
  2. The returned object is the authoritative entity record. Copy or pipe it to your destination.

There is no separate bulk-export operation for entity data beyond repeated get_entity_context calls — treat it as a lookup interface, not a bulk dump tool.

Path 2: Wiki articles as Markdown

Use this for article content you need for downstream publication, processing, or indexing.

Wiki articles are plain Markdown files with YAML frontmatter, stored directly in the media-knowledge-* git repositories. Read or export them the same way you'd export any file from a git repository — clone or pull the relevant repo and read the files you need directly. There is no separate HTTP export endpoint; the git repository itself is the export surface.

Path 3: Ledger entries for audit

Use this for tamper-evident records for compliance, legal discovery, or third-party audit.

Page through GET /v1/entries?since=<cursor> against your service-fs instance until the response is empty, then fetch GET /v1/checkpoint to anchor what you exported to a specific tree_size/root_hash. See Read the command ledger for the full procedure and Verify a WORM ledger entry for confirming what you exported hasn't been altered. The exported entries and checkpoint are both plain JSON, verifiable with a standard SHA-256 utility — no proprietary tooling required.

Choosing the right path

What you need Use path
Information about a named entity (person, project, service) 1 — DataGraph
Article content for publishing or indexing 2 — Wiki Markdown
Tamper-evident records for compliance or audit 3 — Ledger entries

Note: if you're looking for a spatial/GIS export path (co-location clusters, archetype data), that's a separate system this guide doesn't cover — check the GIS-specific documentation for your deployment rather than assuming the generic paths above apply there.

Expected outcome

The data you need, exported through the path that actually matches how the platform stores it — not a fabricated unified export endpoint that doesn't exist.

Verification

For entity data, confirm the returned profile's freshness matches your expectation (see Query the DataGraph). For wiki content, confirm the frontmatter block parses and the slug matches what you expected to export. For ledger entries, verify the checkpoint's tree_size covers every cursor you exported.

Rollback

All three paths are read-only. Nothing to undo.

Next steps

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 →