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
More customers found and followed up with for businesses that cannot afford to forget.
More customers found, followed up with, and kept.
PingFyd is a front desk and a memory for your business. Your phones get answered, every customer gets followed up with, the busywork gets handled, and your website puts you in front of more of the right people. We film and publish the work as we go, so you can see exactly what you are getting.
Underneath sits PING, the system that remembers how your business runs. What a customer told you last spring is still there when you need it, instead of lost in someone's inbox.
This site runs on the same system, and it is still under construction. The maturity labels on this page say what is real today.
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-16Get featured, and get found by more customers.
We feature exceptional local businesses in our Top Ranked groups and on this site, free. A feature puts your name, your work, and your reviews in front of people who are ready to hire, and it costs nothing to apply.
Applying covers your own business. Nominating points us to a business you admire: message us on Facebook with its name. Featuring is free to apply for, and selection is not promised.
The 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.
Explore business demos
/make
The proof is published
Long-form films
We build real systems for real businesses and film what actually happens, start to finish. Multi-hour documentaries, 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 with logs, timestamps, and receipts, so any claim on this site can be checked.
/prove
How we work
Activity is not output.
Work counts when a verified artifact lands in the record.
Evidence outranks reports.
If a summary and the disk disagree, the disk wins.
Finished means verified, not rendered.
Every release passes decode, seam, and hash checks, and a human ear, before it ships.
/offers
What PingFyd can do for your business
Business Spotlight
Exceptional Western Colorado businesses, featured in the Top Ranked groups and on PING's pages. Free to apply.
Apply for a featureFind what is wasting your time and money
A scoped introductory assessment: what is wasting time or money, the root cause, and what would genuinely improve it.
Explore the assessmentDigital Concierge and business websites
An always-on front desk for your business, and a website built from your business understanding. Delivered today as bespoke PingFyd engagements.
See it in ProductsA memory for your business
Systems that remember how your business works and take over the repetitive parts, so the same question stops getting answered three times. In development, applied piece by piece 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 system underneath
PING, the intelligence system behind everything above. Its ambitions are labelled as ambitions: documented, in development, or direction.
Read the technology/truth
The knowledge in your business should not walk out the door every night.
A technician answers the same customer question three times because nothing was written down. Estimates, promises, and preferences live in heads, inboxes, and scattered tools, so every day starts from scratch. PingFyd keeps what your business learns in one place that remembers, and puts it to work.
/how it works
Nothing your business learns gets lost
Every call, job, and customer detail goes in once, gets remembered, and gets more useful over time. What your business figures out this month is still working for you next year. The five steps below are the mechanism, with the evidence attached.
/observe
OBSERVE
It notices what happens.
- · 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
It writes it down, and keeps it.
- · 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
It connects the call to the customer to the job.
- · 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
It does the work, within the limits you set.
- · 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.
What happens becomes a record, the record becomes knowledge, and the knowledge drives the next job. The full loop ran end to end in testing on 2026-09-17, from a proposal through to a checked result. Three wiring gaps are documented honestly 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.
Illustrative model of business relationships, not live data. The generic knowledge graph is built; a business-domain graph is a direction.
Explore a relationship
Choose a node to see what it represents and how it connects.
/receipts
Every answer comes with receipts
A real run, recorded end to end. Follow any answer back to where it came from: what was seen, what it set in motion, and who did the work.
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
/under the hood
The work can happen anywhere. The record stays in one place.
Jobs run wherever there is capacity. What happened, what was decided, and the proof of it land in one record you can check, so the story never splits into competing versions.
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
Every capability on this page is labeled with how real it is today. Ambition never outruns evidence here: stages, not dates, and every number carries the date it was true.
Event plane
LiveGateway healthy, authentication enforced on reads and writes. POST /events bypass closed live; scheduler resumes after restart.
Canonical events
LiveEnvelope validation, append-only store. Trigger rejects UPDATE/DELETE (captured 2026-09-16/17). TRUNCATE not covered.
Tenant registry
BuiltPostgres-backed registration. Multi-tenant isolation not evidenced live.
Knowledge graph
BuiltGeneric graph built and exported.
Neo4j adapter
ExperimentalThin REST adapter, priority 7. Not connected live.
Agents
ExperimentalWorker runtime built. IntelligenceWorker registered dormant. First scoped Hermes WorkOrder executed 2026-09-17 (exit 0, independently verified).
Evidence and witness
BuiltEvidence authority and witness modules built.
Deterministic replay
ExperimentalKernel replay machinery exists. No replay run captured yet.
Multi-runtime convergence
BuiltCaptured 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
DirectionNo business-domain graph subsystem yet.
Oracle execution
ExperimentalLive 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
DirectionNo deployment target yet.
Playbooks and institutional memory
BuiltCaptured 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: watch the work happen
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 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.
PingFyd 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.