Chapter 01 / 06
The scheduled loop
Proprietary market metrics are supported by a recurring evidence process rather than an opaque claim pipeline.
The edge is proprietary. Now the pipeline that finds it is, too.
HtAG’s metric families — RCS™, GSP, GPD — are not in the standard feeds, and its market-selection methodology carries a documented record of 135 recommendations without a loss. Each of those metrics began the same way: substantial research hunting correlations between events and data, between metric and metric, until something survived testing.
The work this used to take
Scanning twelve signal categories — supply, credit, rents, migration, infrastructure, climate, policy, labour — then structuring, de-duplicating and validating what survived. A standing research function, run out of the data team’s calendar between everything else it builds.
The ledger the loop now carries
365 runs a year: 52 weekly signal scans, 26 QA passes, 12 validation rounds against live HtAG data, 4 synthesis labs — 94 research stages on cadence, none of them dependent on anyone’s spare hours, and a heartbeat on every other day.
Where the hours went
The data team builds instead — new metrics, new endpoints on the developer platform, new features and products. The first product seed to come out of the loop, an internal validation-queue app, is already in the store awaiting operator approval.
For the businessSome consequences resist a single number — this one compounds instead. Every validated finding is a candidate metric, skill or product, and the pipeline that used to run on stolen hours now never misses a week.
Workflow context and documented result
HtAG Analytics is known for proprietary market metrics — the Relative Composite Score™, Growth Spillover Effect and Growth Pattern Deviation among 150+ metrics across 7,000+ suburbs. Every one of them began as correlation research: events tested against data, metric against metric, until an edge survived. This loop industrialises that R&D — a live daily orchestrator moves external signals through a fixed evidence ladder, while the data team spends its hours on what only people can build: new metrics, new APIs, new features and products.
A learning system with visible evidence status.
Built inside Morpheus for HtAG Analytics. This case documents the research process and its current evidence status. The scheduled loop builds the record needed to assess future findings.
What starts it
- Answer
- A daily schedule at 21:00 UTC —
0 21 * * *. It wakes whether or not there is work to do.
What it decides first
- Answer
- Which cadence is due today: weekly, fortnightly, monthly, quarterly, or none.
What it produces
- Answer
- Structured hypotheses with an expected direction, the metrics that would test them, a risk caveat and a validation window.
What it holds
- Answer
- One shared evidence store — the canonical state carried between runs, and the reason a Sunday run knows what the previous month concluded.
What it may never do
- Answer
- Publish a claim, produce client-facing material, launch a product, or overwrite the underlying skills. All four sit behind an operator gate.
In the store now
- Answer
- Twelve open hypotheses, moving through four evidence tiers.
Proof status
- Answer
- Customer zero — HtAG Analytics, running to its cadences on the live instance.
End of chapter 1 · The scheduled loop
Related guide in LearningChoosing the first workflow ↗