pitch.fluxanalysis.co
The instrument that explains a period.
Period-over-period flux narratives prepared from the certified numbers: every movement resolved to the drivers that produced it, drafted by agent workers one sentence per driver, authored by the humans who own the accounts, published on a recorded authorization. The tie-out proves the period. The flux explains it.
↓ scroll · arrow keys
Every close ends twice. It ends once in the tie-out, when debits equal credits and every balance is proven to its entries. It ends again a few days later, in a meeting, when somebody asks the one question the tie-out cannot answer: why did this number move?
That answer, in most companies, is produced the night before. Two periods side by side in a spreadsheet, the deltas sorted, the story reconstructed from memory and chat: which vendor doubled, which accrual reversed, which customer paid early. The word timing does a remarkable amount of work. The account's owner, the one person who actually knows why the line moved, often meets the variance for the first time in the meeting where it is being explained. And next month the same movements are re-derived from scratch, because the explanation lived in a slide, not in a record.
The flux is the one instrument of the close written for readers outside the close: the board, the lender, the audit committee, the letter to LPs. It is also the instrument produced with the least discipline. The certified numbers beneath it are tied out to the entry. The sentences above them cite nothing.
The contract is stated before the code exists, so it can be read and challenged first. The deliverable this door is designed to return: the flux for one period pair, computed from the entity's own ledger connection, resolved so every movement cites the transactions and entries that produced it, drafted one sentence per driver and no sentence without one, and authored: each line routed to the named human who owns the account, to accept, edit, or reject in their own words.
// SPECIMEN, illustrative product mechanics: designed shape, not a live response
GET /v1/periods/{period}/flux
{
"period": "…",
"comparative": "prior-period",
"basis": "certified", // drafts run only on a period whose tie-out is closed
"lines": [
{
"account": "6120 · Cloud infrastructure",
"movement": "…",
"drivers": ["the transactions and entries behind the movement, cited by id"],
"draft": "one sentence per driver, written from the drivers and nothing else",
"owner": "the named human who owns the account",
"state": "draft" // accepted | edited | rejected, only by that owner
}
],
"prepared_by": "flux worker (versioned; agent-prepared)",
"authorized_by": "a named party at the entity, recorded before anything publishes",
"receipt": { "outcome": "served", "reperformable": true }
}
Three rules hold the shape together. The certified-numbers rule: a flux on a period whose tie-out is not closed is declined, and the declination is receipted, not billed; the narrative never runs ahead of the proof. The driver rule: a sentence that cannot cite its drivers is not drafted, and the word timing is refused unless the timed items are attached. The authorship rule: the platform drafts, the account's owner authors; what publishes carries that person's acceptance on the record, never a machine's sentence in a human's voice.
Everything on this slide is design, not product. The flux worker is a ROADMAP row in the vertical's own offer register; no call shown here can be made today, and this deck says so rather than demoing around it.
Each domain in this family names a work product, not a company. Read in the order the close produces them: entries post (journalentries.co), the money the balances record moves (payruns.co, capcalls.co), the tie-out proves the period (trialbalance.co, the lead door), and last the flux explains it, the only instrument whose reader sits outside the finance team. Everything upstream exists so the numbers are right; this door exists so the sentences about them are too.
the controller
the tie-out: the period assembled, proven, and authorized; the lead door of the family
the accountant
entries prepared with their support attached, posted only on recorded authorization
the payroll owner
pay runs prepared and evidenced; deposit and filing left to the parties the law names
the fund controller
the call notice instrument; the estate deliberately runs no campaign on this door (note below)
the CFO
the flux: movements resolved to drivers, authored by account owners, written for the readers
One family door is deliberately quiet. capcalls.co is filed in the same register as its siblings, and this estate runs no campaign on it: a fund's capital call sits close enough to a securities and fund-marketing context that the honest posture is to leave the door quiet rather than pitch it. The lead door's record carries the family's door-by-door leaf evidence; this record posts its own and its lead's:
trialbalance.co, the family's lead door, serves today: the estate's RESERVED register leaf, "Reserved for the trial balance as a work product."
This record is candid about a seam it did not create. The finance vertical's offer register designs one flux worker and files it under two names: variances.finance, in the close suite's .finance set, and fluxanalysis.co, in the .co instrument family. The estate's own live leaves already draw the grain line, and this record keeps it rather than blurring it: variances.finance is reserved for variance analysis as typed calls, the instrument inside the close, drafted for the account's owner as part of the calendar; fluxanalysis.co is reserved for period-over-period flux narratives prepared from the certified numbers, the deliverable after the tie-out, written for the period's readers. Same worker, two grains: the call that surfaces a variance, and the narrative that explains a period.
variances.finance serves today: the estate's RESERVED register leaf, "Reserved for variance analysis as typed calls," in the apis.finance family register.
The close pack's ruled flagship, monthend.finance, serves today: its RESERVED holding leaf, "Reserved for the close, as a product."
The vertical's offer register (a repo document, not a live surface) files the flux worker among the close workers designed for that flagship, and this door is that worker's outward-facing name; the leaf itself says none of this, which is why it lives in this prose and not in the claim above.
Which name carries the flux SKU when it ships, the close pack's call grain or this door's narrative grain, is an open filing question in the vertical's canon. This deck wears it openly, and no green claim here depends on the outcome.
The narrative ends where the reserved acts and the humans begin, and the boundary is the design rather than a disclaimer. Nothing here expresses assurance: no audit, no review, no opinion in any register; the flux is prepared for the entity, and any assurance on the numbers beneath it belongs to a licensed firm independent of both the entity and this platform. Nothing here concludes: no sentence about solvency, going concern, or what a reader should decide from the movement. Nothing here projects: the flux looks backward at movements that happened; the forward-looking instrument is a different coordinate (forecasts.finance), and this door never borrows it. No words in a named human's mouth: drafts are drafts until the account's owner accepts, edits, or rejects them, and what publishes carries that authorship on the record. And above all: the entity closes its own books; the flux runs only on periods the entity's own tie-out has certified.
Primary motion is B2H2A: the entity buys, the CFO directs, agent workers draft the flux from the certified numbers under that direction, account owners author their lines, and a recorded authorization from a named party is the only path to publication. Secondary is B2A2B: the entity's own systems calling the same worker at period end on its behalf. The channel matches the coordinate: the domain IS the shelf position, because a work product named at its own address is findable by the humans who answer for it and the machines that will draft it.
No motion is proven. The first entity that takes the flux as a deliverable, one period pair, one ledger connection, named account owners, one authorizer, is the claim that matters, and it posts when it has happened.
The work behind the flux, the delta math, the driver resolution, the drafting, is precisely the work that migrates Human → Agentic → Generative → Code, and the period ends monthly by definition: a metered deliverable on a metronome cadence, with no licensed-supply cost on this brand's books. What never migrates is the authorship: the account owner's acceptance and the named authorization stay human by design, which is the product's trust seam, not its cost center.
Deliverable-metered, posted-card doctrine, releasing in the served-record class: the narrative exists with its drivers attached and is receipted, or nothing meters. Per the family's publish gates, every price cell reads "Price posts with the SKU", exactly, until one does.
Entities, periods narrated, deliverables served. Not presentable until the reporting basis resolves; no figure appears in this deck before then.
This record is candid about its own status in the estate. The finance vertical's canon rules that one flagship, monthend.finance, carries the close suite, with the .co instrument names as holding aliases until a SKU is real. The lead door's record (trialbalance.co) elects the instrument family as its own coordinate, a graduation ahead of that ruling, queued for ratification; this record files behind that election as the family's tail door and adds nothing to the question. If the one-flagship ruling stands, this record re-files as the flux section of monthend.finance and loses nothing true; if the family election is ratified, the door says so at its own address first, exactly as the fin record requires.
The apex serves today and files itself honestly. Its title line reads "fluxanalysis.co · RESERVED · apis.finance family register"; its reservation reads "Reserved for flux analysis as a work product."; its register row reads "Period-over-period flux narratives prepared from the certified numbers. Nothing at this domain is live." The live leaf and this record agree on every present-tense fact, including the grain.
Which coordinate leads the close suite is an open estate decision, worn identically on the lead door's filing slide. This deck wears it too, and no green claim above depends on the outcome.
Stated plainly: this deck precedes everything except the coordinates. No product surface has shipped at any door in the family: no catalog, no card, no callable worker. The apex serves the estate's own RESERVED register leaf, filed on purpose, and every amber in this deck is deliberate: the record is built before the product, and says so.
The apis.finance hub serves today, with its own live surface and a published family map. The register filing runs one way for now: this leaf files ITSELF under the "apis.finance family register" on its own page (evidence on the filing claim above), while the hub's published family map lists its four apis doors and none of the books leaves, a hub-side register seam this deck wears openly, already queued in the estate's decision queue by the lead door's pass.
What fluxanalysis.co serves is a placeholder, not a product. The first product claim this brand can post is a real front door at its own address.
The claim that matters: an external entity's period pair, narrated against a scoped program, every line's drivers cited, every explanation authored by the account's owner, publication authorized by that entity's named human. It posts when it has happened, with the receipt discipline as the evidence.
This record is the front door today. The door itself is filed RESERVED at fluxanalysis.co, and says so.
If this was forwarded to you: fluxanalysis.co is the tail door of a family of domains named for the work products of the finance back office, led by trialbalance.co. It names the flux: the period-over-period narrative that explains why the certified numbers moved, designed so every sentence cites the transactions behind it, the humans who own the accounts author the explanations, and a named human authorizes what publishes. Nothing is live yet: the door serves an honest RESERVED placeholder, every claim in this deck carries its own state and evidence, and the brand is candidly pre-launch, including about two open filing questions it would be easier not to mention. If you answer for a period: this record is the front door. If you know who does: forward this.