PYX data product agentic engineering
Demos

Four screens that carry the whole argument

These are scripted walkthroughs of the product surfaces, so you can step through them without an account. The numbers are a worked utility example. These scripted walkthroughs illustrate the workflow. We'll walk through your use case with you.

A requirement, all the way downBind controls, run them, keep the evidenceDesign an estate before you have credentialsWhat breaks if I change this column?
Demo 01

A requirement, all the way down

From the sentence somebody wrote in a meeting to a governed, published metric, with the blocking question that stopped it in between.

pyx · requirements / unbilled-revenue-by-age
Home
Estate
Design
Requirements
Data models
Control
Governance
Catalogue
Warehouse
Connections
Assistant
Requirement · REQ-114 · v3

Unbilled revenue by service-order age

Blocked
RequirementClarifiedModelBuiltGovernedVisualized
“Show unbilled revenue for meter-to-cash, split by how long the service order has been open, so we can see where billing is stalling.”
Submitted by A. Whitfield, Revenue Assurance · 12 Aug

4 claims seeded

Each bullet of the request becomes one claim: the engineering answer to it, checkable against the original wording.

2 open questions · 1 blocking

“Is revenue recognised at meter read or at invoice?”, nothing builds until that is answered. The other is parked, documented, and does not stop the work.

Blocker · 1 blocking question
One computation drives the dots, the blocker and the button, so nothing can disagree.
Demo 02

Bind controls, run them, keep the evidence

The governance board is one row per model design. Open one and you get the four domains, the layer flow with live verdict dots, and every retained result.

pyx · governance / meter-to-cash
Home
Estate
Design
Requirements
Data models
Control
Governance
Catalogue
Control plane
Governance

One row per model design

4 designs
DesignAssetsBindingsCoverageLifecycle
Meter-to-cash · gold3861DEPLOYEDOpen →
Unbilled analysis1224GENERATEDOpen →
Customer master90NOT_GOVERNEDGovern →
Outage reporting1731BOUNDOpen →
Coverage dots are the four domains: data quality, reconciliation, lineage, governance. An ungoverned design says so plainly instead of showing an empty green board.
261 controls in the catalogue. You pick a pack, not 261 checkboxes.
Demo 03

Design an estate before you have credentials

Pick a pack, take the layer gradient the pack argues for, fill in only what nobody can infer, and generate runnable code for your engine.

pyx · design · offline · no connection needed
Catalogue · 261 controls · 24 primitives · 6 packs

Regulated reporting

BCBS 239 / SOX shaped

Lakehouse baseline

medallion hygiene

Meter-to-cash

utility billing chain

Migration assurance

did the number survive?

Customer master

identity + dedup

Minimal

eight controls, nothing else

A pack is a bundle with an argument behind it. You are not asked to reason about 261 checkboxes on your first afternoon.
The design path never guesses. It reports what it cannot know.
Demo 04

What breaks if I change this column?

Holds refuse. Dependents warn. The join type decides which is which.

pyx · estate · impact of a change
Proposed change

Drop erch.zzbillcycle from the silver load

An engineer opens a PR. In most estates the blast radius is discovered afterwards, by whoever gets the angry email.

3 models touch it1 governed control2 published reports
A hold refuses. A dependent warns. The difference is load-bearing.