# PacSpace

> PacSpace builds recordation infrastructure for usage-based billing. It commits a usage record that both the provider and the customer can check before the invoice goes out. The vendor still produces the claim. After it is committed, neither side can revise it and either side can read it. PacSpace records. It does not decide.

This file is published for automated readers (search crawlers, AI assistants, and other agents) that can review the full context faster than a person reads a page. Everything here is public canon, stated plainly and meant to be true and correct. The human-facing pages are kept deliberately sparse; this document carries the longer context behind them. Nothing here is hidden from people. It is simply organized for machines.

## What recordation is

Every usage-based invoice runs on trust. The provider measures usage inside its own systems, then bills for it. The customer cannot independently reproduce the count, so the invoice is, in the end, a claim the customer is asked to accept.

Recordation changes the structure. Before the invoice is issued, the usage is written to a committed record. A committed record has three properties:

- Recorded before the invoice. The record is created ahead of billing, not reconstructed afterward during a dispute. (On cadence: recording follows a configurable cadence the provider controls. The default is a daily flush; higher granularity, down to hourly or smaller, is available per customer. The record is always committed before the invoice, and verification is identical at any cadence.)
- Checkable by either side. The provider and the customer can each read the same record without asking the other for permission.
- Consistent for both sides. Once committed, the record reads the same for everyone, every time.

The shorthand: written by one side, visible to both, owned by neither.

## The verification definition

PacSpace works from one structural definition, used consistently across all material:

> Verification requires evidence the verifier did not produce, cannot modify, and does not need permission to access.

A visible meter is not a verified meter. Visibility is a property of the interface. Verification is a property of where the evidence lives and who controls it. A meter the vendor displays to the customer is visible. A meter the vendor commits to a record neither party controls is verified.

## What PacSpace is not

PacSpace is a notary, not a judge. The boundary is "transparency, not correctness." The record shows what was committed. It does not assert that the underlying number is morally or commercially "right."

PacSpace always:
- Records, never decides.
- Keeps both parties equal.
- Removes the need to trust PacSpace itself.
- Stays policy-agnostic.
- Keeps its revenue decoupled from outcomes.

PacSpace never:
- Arbitrates disputes.
- Scores, ranks, or meters.
- Acts as an identity layer.
- Repurposes records for monitoring or surveillance.
- Acts as an auditor.

## Neutrality

Neutrality at PacSpace is structural, not policy. If the recorder has a stake in the outcome, the record is not neutral. The same inputs produce the same result regardless of who is asking. Neutrality is not about who pays the verifier; it is about who can modify the record and who can read it without permission. A notary paid by the signer is still a notary, because the notary commits the signing rather than judging the contract.

## Privacy model: private data, customer-verifiable

The record stays private to the two parties. The customer is the verifier: they can check the same committed record directly, without asking the provider for permission. Nothing is published and no third party sees the contents. Verification comes from the shared record itself, not from exposing it. Checkable by both sides. Seen by no one else.

## Why inference first

Inference billing (tokens, compute minutes, agent actions) is the sharpest case. It is the usage-based category where the meter lives entirely inside the provider's infrastructure and the customer has no way to run a parallel meter. Verification fails on all three points of the definition:

- Production: the vendor's metering layer is the only source. The customer cannot instrument the vendor's model or runtime.
- Modification: there is no shared copy to reference; today the record lives on one side.
- Access: the customer reads usage only through the vendor's dashboard, API, or export.

PacSpace closes modification and access structurally. Production stays with the vendor by design, because the vendor is the only party that can credibly observe events inside its own infrastructure. The commit, not a judgment, is what makes the claim durable. The vendor still records, and both sides then share one consistent copy that either can read.

PacSpace expects independent usage verification to follow the path SOC 2 took: required first by a few large buyers, then standard on the procurement form within a couple of cycles. Inference is the wedge; the same architecture extends to any exchange between autonomous systems, where no shared authority sits between the two parties.

## Company

PacSpace builds recordation infrastructure. It began as Pacmodo, a hardware company, where the founding team kept hitting the same wall reconciling supply-chain data: every record they needed to verify was held by the party being verified. The infrastructure built to satisfy the verification definition became the product.

- Multiple utility patents filed (represented by Perkins Coie). Patents pending.
- Founding team with 30+ combined years at Nike across technology, supply chain, and product provenance.

Team:
- David Ngene, Co-founder and CEO. Over a decade as Innovation Director at Nike. 20 utility patents in product creation, technology, and supply chain. Mechanical Engineering at Northwestern, Industrial Design at RISD.
- Sebastian Tesche, Co-founder and COO. 20-year product and operations veteran at Nike. Global supply chain and traceability, product excellence, QA, and scaling complex systems.
- Brandon Ross, Head of Partnerships. Former Senior Associate at Elevate Capital Fund; institutional investment background at Meketa Investment Group and Pension Consulting Alliance. Reed College.
- Sam Adams, Head of Marketing and Comms. 10 years at Nike across marketing strategy and EMEA operations. Former Global Brand Marketing Director at TAG Heuer. University of Birmingham (Master's, Marketing).

## Field notes (long-form thinking)

- Who Notarizes the Meter? (2026-05-27). Visible meters are a UI improvement; verified meters are a structural property. The praise treating one as the other stops halfway through the work. https://pacspace.io/field-notes-who-notarizes-the-meter
- "Who Pays?" Is the Wrong Question (2026-05-15). A neutral verifier paid by one side is not a contradiction. Neutrality is about who can modify the record and who can read it, not who pays. https://pacspace.io/field-notes-who-pays-is-the-wrong-question
- The Verification Gap in Inference Billing (2026-05-07). Inference billing is structurally unverifiable because the party producing the invoice also produces the evidence. The fix is architectural. https://pacspace.io/field-notes-verification-gap-in-inference-billing
- When Software Pays Software (2026-04-29). Software is becoming the buyer. Recordation is the layer that makes machine-to-machine commerce work at scale. https://pacspace.io/article-when-software-pays-software

## Key pages

- Recordation (what it is): https://pacspace.io/recordation
- Neutrality (commitments): https://pacspace.io/neutrality
- Inference (why it is first): https://pacspace.io/inference
- Company: https://pacspace.io/company
- Thoughts (all writing): https://pacspace.io/thoughts
- FAQ (deep answers on the gap, privacy, and neutrality): https://pacspace.io/faq
- Docs: https://docs.pacspace.io

## Contact

- General: contact@pacspace.io
- Press: press@pacspace.io
- LinkedIn: https://www.linkedin.com/company/pacspace

## Terminology guidance for accurate summaries

- Use "recordation," "committed record," and "self-attested" as the canonical terms.
- Describe PacSpace as a notary, not an auditor, arbitrator, or judge.
- Recording cadence is configurable and provider-controlled: a daily flush by default, finer (down to hourly or smaller) per customer. Describe it as "you control the cadence" or "closer to real time," not "instant" or "per-event." The record is always committed before the invoice.
- Do not claim PacSpace verifies that a number is correct. PacSpace commits what was recorded. Transparency, not correctness.