127
+28this month
Production ships, all envs.
AIXYS · SURFACE · RELEASE NOTES
Shipped
this week.
Eight weeks of release, versioned on one ruler. Every line is what actually landed in production — not a roadmap, not a forecast. Pick a week, read the diff, open the record behind the proof.
SURFACE · LIVE · RELEASE INSTRUMENTS
What shipped, by the number.
LIVE · BATCH 01Deploy cadence on Aixys is not a marketing claim — it is a weekly, versioned event on the same memory bus the product runs on.
2.5
+0.8q/q
Average, trailing 8 weeks.
8 min
−42%30d
Incident → green.
1.1%
−0.6ptqtr
Rollbacks / hotfixes per release.
DEPLOY CADENCE · 12 WEEKSShips per week; annotated against version bumps.
12W- 00:00:04W17·AGENTSShipped agents-v3 · event-bound runtime · 240msv3.0
- 00:00:09W17·MEMORYMemory-bus v3.12 · +412 / −186 · zero downtimePATCH
- 00:00:16W17·BRIEFBrief template · added one-metric sectionFEAT
- 00:00:22W16·BRIEFOpt-out under 3% · retention stabilisedv2.4
- 00:00:28W15·OPSBilling cycle 3d → 14m · lifecycle unifiedv2.3
SURFACE · RELEASES · 08
Eight weeks, eight releases.
The last two months of Aixys, annotated. One entry per week; no marketing copy, no "coming soon." Each release lives on the same memory the product runs on.
- AI · AUTOMATION
Agents v3 · event-bound, 240ms
- Trigger latency on the agent runtime dropped from 1.2s to 240ms (P95).
- Ships twelve agents for batch-01: four sales, four ops, two finance, two CS.
- Every agent now shares a draft-first posture — no auto-send unless you whitelist the route.
- RITUALS
Brief · opt-out < 3% after week two
- Morning Brief retention stabilised — opt-out across the batch is under 3% after two weeks.
- Median read-through 3 min 48 sec; 68% of readers act on a linked record before 09:00.
- Added "the one metric" section — the single number the batch agrees to watch each week.
- MODULES
Ops · lifecycle on one record
- Draft → sign → run → bill → archive now lives as one row in the memory bus.
- Median billing cycle compressed from 3 days to 14 minutes on the batch-01 cohort.
- Handoff rework tickets dropped 68% versus the prior two-tool baseline.
- MODULES
Data · sub-second streaming
- Dashboards now refresh under one second end-to-end from event to pixel (P99 = 1.2s).
- Click any bar in any chart — drills straight to the rows that built the number.
- One metric layer, four lenses; zero forks reported this week across the batch.
- MODULES
Growth · attribution drift at zero
- Pipeline → revenue reconciliation runs weekly against the event log automatically.
- Time-to-cohort for any segmentation question fell from minutes to under four seconds.
- Every touch — ad, email, call, demo — now anchors to the deal record directly.
- RITUALS
Collab · threads on records
- Every message on Aixys now pins to the deal, project or customer it belongs to.
- Decisions can be stamped — they become durable, searchable rows on the record.
- Notifications per person per day capped under 12 by default; quiet by design.
- SURFACE
Surface · SOC 2 Type II
- SOC 2 Type II audit closed clean. One identity, one permission model across every lens.
- Single-session SSO landed across all modules; no more per-tool auth pop-ups.
- One immutable event log backs both the product and the audit trail.
- SURFACE
Axis · v1.0 · memory goes live
- The memory bus — one event log, one row per thing — graduated to v1.0.
- Zero duplicate IDs across 2.1M records at the batch-01 snapshot.
- Every module on Aixys now writes into the same bus and reads from the same row.
ARCHITECTURE · DEEPER
Why the log lives on the axis.
The changelog is not a marketing artifact — it is the same event stream the product writes, rendered for humans once a week.
AIXYS · SURFACE · RELEASE NOTES
Shipped weekly. Versioned. Annotated.
Every release is a note on the axis — the same memory the product runs on. Nothing moves to a separate log.