TenantOS
From HPP to PING
This site was rebuilt from a trades-company website into the first TenantOS tenant. The transformation is the proof of concept.
/live
Continuity infrastructure for AI agents and the businesses they serve.
Inspired by the best of the best.
PING helps exceptional people and businesses get recognized, work smarter and put technology to practical use. We start by listening, understanding how things really work and finding improvements that make a measurable difference.
Nominate a business for a PING feature.Apply to be considered for a feature.Explore a practical technology and operations assessment.
Applying covers your own business. Nominating is how you point us to a business you admire: message PING on Facebook and tell us its name. Featuring is free to apply for, and selection is not promised.
A serious production studio with profoundly unserious ideas.
PING builds real things with autonomous systems, films what actually happens, and publishes the evidence. Cinematic investigations into the hidden systems shaping our future, where we build, break, test, and explain the technology ourselves.
PING turns information into reliable understanding, understanding into useful action, and action into evidence that can be trusted and replayed.
This site is a live TenantOS tenant. The runtime behind it is under active construction. Maturity labels on this page say what is real.
Evidence card
BuiltCaptured 2026-07-28
OBSERVED
replaying captured recordNew lead submitted
Something happened. Recorded with timestamp and source.
- event_type
- LEAD_CREATED
- event_id
- e9591d72…ce5864c5
- recorded
- 2026-07-28T02:10:54Z
RECORDED
Canonical event stored
The event became the source of truth. 770 events in the run.
- envelope
- canonical-event-envelope v1.0.0
- store
- append-only
TASKED
Mission created: LEAD_FOLLOWUP
The event triggered a mission, the objective to pursue.
- mission_id
- 51009ceae9ef316a
- priority
- 3
EXECUTED
Workers ran
150 worker executions completed in the commissioning run.
- executions
- 150
- scenarios
- 14
A captured record from PING's own commissioning run. Not live activity. Full lineage lives in the runtime, not on this page.
ping-gateway: healthy at capture · constitution 1.0.0 · auth enforced on reads
Captured · probed 2026-09-16The logos on this page belong to their respective owners, shown for identification and free promotion only. This site is not affiliated with, endorsed by, sponsored by, or officially connected to any business displayed.
/make
What we make
Long-form films
Multi-hour documentaries produced by a supervised agent factory, with every finished minute verified before it counts.
Shorts
One idea, one proof, one payoff. Clips are cut only from finished, accepted footage.
Investigations
The engineering behind the films, published as annotated breakdowns with logs, timestamps, and receipts.
/prove
How we work
01
Activity is not output.
Work counts when a verified artifact lands in the record.
02
Evidence outranks reports.
If a summary and the disk disagree, the disk wins.
03
Finished means verified, not rendered.
Every release passes decode, seam, and hash checks, and a human ear, before it ships.
01
Activity is not output.
Work counts when a verified artifact lands in the record.
02
Evidence outranks reports.
If a summary and the disk disagree, the disk wins.
03
Finished means verified, not rendered.
Every release passes decode, seam, and hash checks, and a human ear, before it ships.
/offers
What PING offers
Business Spotlight
Exceptional Western Colorado businesses, featured in the Top Ranked groups and on PING's pages. Free to apply.
Apply to be considered for a feature.Practical technology and operations assessment
A scoped introductory assessment: what is wasting time or money, the root cause, and what would genuinely improve it.
Explore a practical technology and operations assessment.Digital Concierge and business websites
An always-on front desk for your business, and a website built from your business understanding. Delivered today as bespoke PING Social engagements.
See it in ProductsOperational Memory and Automation
Systems that remember how your business works and automate the repetitive parts. In development, applied incrementally through engagements.
See it in ProductsOngoing Improvement partnership
A partnership posture, not a packaged product: keep improving what is working, and measure the difference over time.
Start a conversationThe PING Platform
The intelligence system underneath everything. Its ambitions are labelled as ambitions: documented, in development, or direction.
Read the technology/truth
Most AI starts from zero every session. PING starts from everything that happened before.
A technician answers the same customer question three times because nothing was written down. The business knows things, but the knowledge lives in heads, inboxes, and scattered tools. It does not compound. PING is infrastructure for turning activity into durable organizational intelligence.
/observe /remember /connect /act /prove
The closed compounding loop
(so knowledge compounds instead of evaporating) Information enters as raw input and moves through a loop that makes it increasingly useful. Every cycle produces new evidence, which feeds the next cycle.
/observe
OBSERVE
Something happened.
- · Raw input: a call, an email, a form, an API.
- · Recorded with timestamp, source, and version.
- · Nothing silently dropped at the door.
Built
/remember
REMEMBER
Recorded, immutable.
- · Canonical events with envelope validation.
- · Append-only store, now DB-enforced: the trigger rejects UPDATE and DELETE. TRUNCATE is not covered.
- · Reads and writes require authentication, enforced live.
Live
/connect
CONNECT
Relationships, not just documents.
- · A customer called. That created a lead, which became a project.
- · Generic knowledge graph built and exported.
- · Business-domain graph is direction. Neo4j adapter is experimental.
BuiltExperimentalDirection
/act
ACT
Agents act inside capability grants.
- · Missions run live on Oracle: LEAD_FOLLOWUP completed end to end through the patched event door, plus real Python and agent work orders (captured 2026-09-16/17).
- · Worker runtime built. 150 executions in the captured 2026-07-28 run. Retry/dead-letter path verified live: 12/12 assertions.
- · IntelligenceWorker registered dormant. Off until needed.
LiveExperimental
/prove
PROVE
Every answer shows its work.
- · Evidence chain: event, mission, agent, action, result, witness, lineage.
- · Witness records attest who acted under what authority.
- · Deterministic replay machinery exists. No replay run captured yet.
BuiltExperimental
/prove → /observe
THE LOOP CLOSES
New evidence feeds the next cycle.
Observation → Evidence → Event → Knowledge → Action → New evidence. Playbooks ran end to end in test scope on 2026-09-17: proposal, approval, activation, execution, outcome, then a revision that waits on Nolan, then replay and witness. Three wiring gaps are documented in the matrix.
Built
RAW INPUT
email · call · document · form · API
RAW INPUT
email · call · document · form · API
OBSERVATION
something happened
EVIDENCE
source + confidence
CANONICAL EVENT
recorded, immutable
KNOWLEDGE
verified understanding
BUSINESS GRAPH
relationships
PLAYBOOK
learned procedure
AUTOMATION
agent acts
NEW EVIDENCE
result recorded
↺ feeds back to observation
/connect, rendered
See your business
The Connect beat as a canvas. A customer called. That created an event, which created a lead, which became a project. Every node knows its neighbors.
Hover or tap a node to see what PING knows about it.
Illustrative model of business relationships, not live data. The generic knowledge graph is built; a business-domain graph is a direction.
CUSTOMER
The person or business. Identity persists across every interaction.
EVENT
A call came in. Recorded as canonical event E-01J with timestamp and source.
PROPERTY
The site. Address, access notes, history of every visit.
LEAD
Created from the event. Status, source, and every touchpoint tracked.
PROJECT
The job. Scope, schedule, documents, and decisions in one place.
PERSON
Assigned technician. Skills, availability, and past work on this property.
SERVICE
What was sold. Linked to estimate, parts, and warranty terms.
ESTIMATE
The quote. Line items, version history, and approval state.
JOB
Scheduled work. Who, when, what was done, and the evidence.
REVIEW
The outcome. Linked back to job, person, and customer.
On desktop this renders as an interactive graph. The relationships: customer called (event), owns (property); event created (lead); lead became (project), assigned (person); project needs (service); service priced (estimate); estimate approved (job); job rated (review).
Illustrative model, not live data. The generic knowledge graph is built; a business-domain graph is a direction.
/prove
Every answer comes with receipts
(so every answer can show its work) An annotated record from a real captured run. Tap through the lineage: the observation, the event, the mission it caused, the workers that ran.
Annotated event record
BuiltCaptured 2026-07-28
- event_type
- LEAD_CREATED
- What happened, in the canonical vocabulary.
- event_id
- e9591d7277246b27eb090abb2acece5864c58d8dcaf94701286c6f40ccd33153
- The permanent identifier. Quote it and the record can be found.
- recorded
- 2026-07-28T02:10:54Z
- When it landed. Timestamps are part of the evidence.
- source
- PING commissioning run, 14 scenarios, 770 events
- Where it came from. Provenance is not optional.
- caused
- mission 51009ceae9ef316a · LEAD_FOLLOWUP · priority 3
- What it triggered. Every event links to its consequences.
- executed
- 150 worker executions completed in the run
- What the system did with it. Results attach to the same lineage.
A captured record from PING's own commissioning run. Not live activity.
Execution receipts · one authority, two runtimes plus an exterior agent
Captured 2026-09-16/17- python capability
- mission bfe815990337e45d · PYTHON_CAPABILITY_RUN · event 27482dbdabfb57b7190dd9f4ae530bee98ff381c8cc0eebec27349dd04b502a1 · task e694f5787ad45764 · evidence 49a96bff42cb1bdf5bc19dd56901a1955a0fb962a24d498dc36a21d0bd7e180e · result sha 1945b844ac504c8fbd631b668b4ede93291b432c573f7263f631e7f63ae521ab
- A real Python capability executed a PING task against live Oracle Postgres: 44/44 assertions, zero Python-emitted events. Not a fleet yet.
- exterior agent
- Hermes WorkOrder 0d598aef352b9a8a · text.transform · exit 0, independently verified · result sha f0b021848c2ddc7d6e07b8f8e186c78259454a935153804c7b4c574ec5bb1eed · PING events f326ea70d7cf16ce85c4cc56a23bc147ce0273984023c123b8b5467ea6d507de / e91681bfd300389e9c8f10c7c3ad2f9cea352342bfe6aa71f962d14c764bb587 / daaa75fc5b298c5b7fedab679e8bbf8a792099afc779877dd3d8acc7def1bf92
- One scoped execution, not a fleet. Codex was quota-blocked; OpenCode has no headless CLI. Adapter code is uncommitted worktree code, not a live worker runtime.
Captured receipts from the convergence sprint. Not live activity.
The evidence chain
EVENT E1
Something happened. Recorded with timestamp, source, and version.
MISSION M1
The event triggered a mission: the objective to pursue.
AGENT A3
The agent assigned, with explicit capability grants.
ACTION
The concrete operation the agent performed.
RESULT R1
What the action produced, with evidence attached.
WITNESS W1
The permanent attestation: who, what, when, with what authority.
LINEAGE L1
The full chain, queryable. Every step links to its cause.
Replay
- E1 + runtime / version / context
- re-execution
- compare
- MATCH / DIVERGENCE
Important automation leaves enough evidence to answer:
- → what happened
- → what caused it
- → which agent acted, with what authority
- → what evidence existed
- → whether behavior replays cleanly
/run
One authority, many runtimes
(so execution can spread without truth splitting) Workers: where tasks run. The event plane: where truth lands. Authority: what decides. What PING provides: canonical events, capability grants, evidence. What that guarantees: execution can move without truth splitting.
Ping Authority
capabilities · identity · canonical state
JS WORKERS
Built
Deterministic task execution in the PING runtime. 150 executions in the captured commissioning run (2026-07-28).
PYTHON WORKERS
Built
A real Python capability (python.canonical_hash) executed a PING task against live Oracle Postgres: 44/44 assertions, zero Python-emitted events (captured 2026-09-16/17). Adapter code is uncommitted worktree code, not a live worker runtime.
EXTERIOR AGENTS
Experimental
Codex, Hermes and similar workers are exterior agents, not PING subsystems. First scoped execution captured 2026-09-17: Hermes WorkOrder 0d598aef352b9a8a, exit 0, independently verified, three canonical PING events. One execution, not a fleet.
Result / Evidence
returns to PING authority
Execution locations: same authority model
LOCAL
Built
ORACLE
Experimental
CLOUD
Direction
Built
The convergence itself, one canonical event handled by multiple runtimes under one authority, is captured (2026-09-16/17): the JS mission runtime plus a Python executor plus a scoped Hermes WorkOrder, with shared evidence lineage. Not a fleet yet. Status labels reflect evidence, not aspirations.
/status
What is real
(so ambition never outruns evidence) Every capability on this page carries its maturity. Stages, not dates. Captured evidence is labeled captured; every number carries its as-of date.
Event plane
Gateway healthy, authentication enforced on reads and writes. POST /events bypass closed live; scheduler resumes after restart.
Canonical events
Envelope validation, append-only store. Trigger rejects UPDATE/DELETE (captured 2026-09-16/17). TRUNCATE not covered.
Tenant registry
Postgres-backed registration. Multi-tenant isolation not evidenced live.
Knowledge graph
Generic graph built and exported.
Neo4j adapter
Thin REST adapter, priority 7. Not connected live.
Agents
Worker runtime built. IntelligenceWorker registered dormant. First scoped Hermes WorkOrder executed 2026-09-17 (exit 0, independently verified).
Evidence and witness
Evidence authority and witness modules built.
Deterministic replay
Kernel replay machinery exists. No replay run captured yet.
Multi-runtime convergence
Captured 2026-09-16/17: the JS mission runtime plus a Python executor plus a scoped Hermes WorkOrder, one authority, shared evidence. Not a fleet yet.
Business graph
No business-domain graph subsystem yet.
Oracle execution
Live on Oracle (ping-core-01, native arm64). Backup set created on-box 2026-09-17: pg_dump, Qdrant snapshot, clean source tarball. Same host only, no automation yet.
Cloud execution
No deployment target yet.
Playbooks and institutional memory
Captured 2026-09-16/17: proposal to approval to activation to execution to outcome to a revision gated on Nolan, then replay and witness, all in test namespace. Three wiring gaps documented.
/watch · Latest from the studio
The Long Ping: the show that tests the thesis
Long-form films about the systems everything else depends on: how they fail, why they fail that way, and what remembering changes. Watch the newest film, or take an episode as audio or as a written transcript series.
/follow · newsletter
Follow the build
Notes on continuity, agents, business systems, and building PING in public. One email when there is something worth saying. No spam, no fluff.
Follow the Build
Notes on continuity, agents, business systems, and building PING. One email when there is something worth saying.
Talk to us about your business.
PING Social helps real businesses put AI to practical use: fewer missed opportunities, less busywork, systems that remember. Currently onboarding Western Colorado home-service businesses.
PING. We build it, we break it, we show the receipts.