All pages
290 articles total.
A
- About PointSav Knowledge
- AEC interface conventions
- AEC muscle memory and interface patterns
- AGENTS
- AI routing and the linguistic air-lock
- Anti-homogenization discipline
- API key boundary discipline
- app-console-email — communications cartridge
- app-console-keys — console chassis and F-key framework
- app-console-slm — inference infrastructure monitoring console
- app-mediakit-marketing — WordPress-leapfrog marketing landing server
- applications/app-console-input
- applications/app-mediakit-knowledge
- applications/bim-and-real-property-surfaces
- Architecture decisions
- Architecture Overview — PointSav Platform
- architecture/capability-based-security
- architecture/collab-via-passthrough-relay
- architecture/diode-standard
- architecture/five-stage-supply-chain
- architecture/foundry-doctrine-architecture
- architecture/leapfrog-2030-architecture
- architecture/machine-based-auth
B
- BCSC continuous-disclosure posture
- BIM design philosophy
- BIM market context and regulatory landscape
- BIM objects — substrate
- BIM objects — three composition layers
- BIM objects — what they are
- BIM token taxonomy
- Brand typography and print standards
- Brand-family swatch
- Browser developer workbench
- Business clustering service
C
- Canadian-simple copyright posture
- City code as composable geometry
- Co-location methodology
- Co-location Tier Nomenclature
- Co-location Tier Nomenclature
- Code for machines first
- Collaboration via passthrough relay — substrate pattern
- Compute substrate
- Contact
- Contributing to PointSav Knowledge
- Crypto Payment and License Issuance Architecture
- Cryptographic ledgers
- Cryptographic payload attestation
- Customer hostability
- Customer-first ordering
- Customer-owned graph IP
D
- Data Overview — Location Intelligence and GIS Data Layers
- Data sovereignty and zero-state telemetry
- Data vault bookkeeping substrate
- Decode-time constraints
- Design color foundations
- Design motion foundations
- Design spacing foundations
- Design system philosophy
- Design system — primitive vocabulary rationale
- Design typography foundations
- Design-system substrate
- Deterministic parser
- Developer Guide Index
- Development regions
- Direct-payment settlement
- Disclaimers
- documentation.pointsav.com goes live — 2026-04-27
- Doorman protocol
E
- Economic model — community and SMB customer tiers
- Edge deployment and boundary ingest
- Editorial language registers
- Editorial philosophy
- Egress service
- Elastic Compute #1 nightly LoRA training pipeline
F
- Favicon matrix and tab identity
- Federation via content mounts
- Fleet aggregator
- FS anchor emitter
- FS architecture and the WORM backbone
- FS data lake
- FS security and compliance posture
G
- Getting Started with the PointSav Platform
- GIS as a BIM substrate
- GIS orchestration application
- governance/compliance-and-continuous-disclosure
H
- Hardware reference
- How to add a node to a running fleet
- How to authenticate binary downloads
- How to build a co-location map
- How to configure a tenant namespace
- How to configure the Doorman gateway
- How to connect to the OSM data pipeline
- How to deploy a knowledge instance
- How to enroll a PPN node
- How to explore the console for the first time
- How to export structured data from the platform
- How to federate archives via content mounts
- How to install the development toolchain
- How to issue a capability token
- How to navigate the console TUI
- How to open your first Totebox session
- How to pair a new device
- How to query the DataGraph
- How to read and write Totebox archives
- How to read the command ledger
- How to rotate keys and capability tokens
- How to run local SLM inference
- How to run your first SLM query
- How to scale user access tiers
- How to self-host a deployment
- How to use declarative knowledge mounts
- How to use the F-key cartridge model
- How to verify a WORM ledger entry
I
K
L
- Learning Datagraph — SLM trajectory loop and apprenticeship queue
- Legal and IP structure
- Location intelligence platform
- Location intelligence platform — strategy and architecture
- Location intelligence UX design philosophy
- Location intelligence UX design philosophy
M
- Mailbox atomicity — flock-based prepend and msg-id idempotency
- Merkle proofs as a substrate primitive
- Message courier service
- Model tier discipline
- Moonshot initiatives
- Multi-engine session coordination — session locks, boot_id, and role guards
N
O
- Ontological governance
- Open BIM and regulatory acceptance
- Open BIM and regulatory acceptance
- OS Mediakit
- OS Network Admin
- os-console Internal Architecture
- os-console platform and cartridge architecture
- os-infrastructure — PPN Node Operating System
- os-privategit browser workbench
P
- Parking Structures (PKS)
- patterns/deployment-patterns
- patterns/knowledge-wiki-leapfrog-architecture
- patterns/pairing-as-permission
- Per-user build cache discipline — preventing cross-user Cargo races
- Personnel and permissions
- Places filtering service
- Platform architecture overview
- POI data schema
- PointSav architecture 2030 — an overview
- PointSav encyclopedia — glossary and lexicon
- PointSav GIS engine
- PointSav Media Kit
- PointSav Private Network
- PointSav Software Distribution Substrate
- PointSav — company overview and three-organisation structure
- PointSav-LLM
- PPN Architecture Overview
- PPN Distributed VM Fabric
- PPN Hypervisor Resource Pool
- PPN Tenant VM Isolation
- PPN VM Resource Pool Architecture
- Pre-commit defense in depth — secret scan, size guard, helper-only gate
- Private Binary Download Endpoint for Paying Customers
- Private Git OS
- Procurement overview
- Professional Centres
Q
R
- reference/structural-positioning
- Regional Name Resolution Architecture
- Retail Anchor Co-location Composition as a Spatial Leading Indicator of Commercial Activity
- Retail anchor co-location composition as a spatial leading indicator of commercial activity
- Root files discipline
S
- Security overview
- Seed taxonomy as SMB bootstrap
- service-input
- service-pointsav-link
- service-slm graph store migration
- services/archetypes-and-chart-of-accounts
- services/service-content
- services/service-email
- services/service-people
- services/service-search
- services/service-slm
- services/service-wallet-settlement
- Single-boundary compute discipline
- SLM and Yo-Yo operational state
- SLM as Totebox sysadmin and support centre
- SLM operationalization plan
- SLM Rust stack architecture
- Source-of-truth inversion
- Sovereign compliance appliance
- Sovereign Mesh
- Sovereign replacement initiative
- Spot VM Lifecycle — Single Controller and Kill Switch Pattern
- Style guide — architecture
- Style guide — changelog
- Style guide — chat
- Style guide — CLA
- Style guide — contract
- Style guide — email
- Style guide — guide
- Style guide — inventory
- Style guide — license explainer
- Style guide — meeting notes
- Style guide — memo
- Style guide — policy
- Style guide — README
- Style guide — terms of use
- Style guide — ticket comment
- Style guide — topic
- Substrate-native compatibility — why the Action API shim was dropped
- substrate/four-tier-slm-substrate
- substrate/knowledge-commons
- substrate/knowledge-graph-grounded-apprenticeship
- substrate/llm-substrate-decision
- substrate/location-intelligence-substrate
- substrate/mcp-substrate-protocol
- substrate/reverse-flow-substrate
- substrate/sel4-microkernel-substrate
- substrate/sovereign-ai-commons
- substrate/substrate-without-inference-base-case
- substrate/tui-corpus-producer
- substrate/yo-yo-lora-training-pipeline
- substrate/yoyo-compute-substrate
- systems/console-os
- systems/os-workplace
- systems/totebox-os
T
- Telemetry architecture
- Template ledger
- The adapter composition algebra
- The apprenticeship substrate
- The asset-anchored BIM vault
- The brief queue substrate
- The building design system for the built environment
- The capability ledger substrate
- The citation substrate
- The compounding Doorman
- The compounding substrate
- The Customer-Tier Catalog Pattern
- The disclosure substrate
- The flat-file BIM leapfrog
- The Genesis Protocol
- The Input Machine
- The language-protocol substrate
- The moonshot-toolkit Build Orchestrator
- The organizational knowledge graph — ontological memory for business operations
- The OS family — eight operating systems, one substrate
- The PPN Command Protocol
- The Private Platform Network: Pooled Compute from Hardware You Already Own
- The property manager BIM gap
- The seL4 AArch64 QEMU Substrate Target
- The six-tier sovereignty matrix
- The sovereign airlock
- The system substrate architecture
- The three layers of a BIM token
- The Three-Stage Editorial Pipeline
- The tiered inference gateway — local-first AI routing
- The trajectory substrate
- Three-dimensional asset token
- Three-layer architecture
- Three-layer stack
- Three-ring architecture
- Three-tier contributor model
- Tier 0 customer-side sovereign specialist
- Tier c key wiring
- Totebox Archive
- Totebox orchestration
- Totebox orchestration as the development environment
- Totebox session
- ToteboxOS
U
V
- Verification surveyor
- Vertical seed packs marketplace
- Vertical Warehouse (VWH)
- VM-* Architecture and OS Family
W
- What is a BIM token
- Wiki component library
- Wiki dark mode
- Wiki provider landscape
- Wiki typography system
- Wikipedia leapfrog design — muscle memory and 5% headroom
- Workspace services slice — cgroup partitioning for multi-developer environments
- WORM ledger design
- WORM ledger storage architecture
- WORM ledger substrate: four-layer architecture