Repository navigation
Brand Foundation
This page sets out why fiscalclock's identity exists, who it serves, how it should feel, where it stands among other tools, and the one idea the whole identity is built on.
Last reviewed: 1 Nov 2026
A brand foundation is the short list of answers that every visual and written choice can be checked against: who we are talking to, what we want them to believe, and what we refuse to say. Without it, a logo, a colour or a sentence is a matter of taste; with it, a reviewer can ask "does this fit?" and get the same answer from anyone. Every choice on the other design pages traces back to this page and to the decision log.
fiscalclock computes dates that end up in financial reports, and its method is to show its correctness rather than claim it: cited sources, independent generators and byte-identical output in three languages. The identity's job is to make that method visible and otherwise stay out of its way (research brief).
The owner chose all of these groups, with no single primary one (DD-002). The identity therefore has to read as credible to an accountant and as precise to an engineer.
| Group | What they come for | What the identity must do for them |
|---|---|---|
| Developers in Rust, Python and JavaScript | One definition, the same results in their language, clear errors (README). | Show code and real output first; keep the three languages visibly equal. |
| Finance and analytics teams | Which fiscal quarter a date is in, when Q3 ends, whether a year has 53 weeks (PDR). | Look trustworthy and plain; draw calendars to scale; write dates unambiguously. |
| AI agents and the people who use them | A contract they can read, answers they can check, and errors they can correct from (Agents-and-MCP). | Keep text and structure machine-readable; describe what is built and what is planned, without hype. |
Non-programmers rarely read the docs; docs are written for people who write code, with plain-English explanations in support (DD-003).
The owner set five sliders, each from 1 to 5, all at 2.5: balanced, leaning very slightly towards the first word of each pair (DD-006). The decision log reads this lean as "calm and precise, but not cold", and records that reading so the owner can correct it.
| Slider | Position | What it means in practice |
|---|---|---|
| Serious – friendly | Slightly serious | Plain statements and second person; no jokes, exclamation marks or slogans in docs. |
| Technical – approachable | Slightly technical | Lead with the definition, the JSON and the error code; explain them in plain words underneath (DD-003). |
| Minimal – rich | Slightly minimal | Neutral surfaces, one accent, no shadows (DD-013, DD-019). |
| Classic – modern | Slightly classic | A conventional docs layout, because simple, familiar structure is judged more trustworthy than novel layouts (trust research). |
| Quiet – distinctive | Slightly quiet | Distinctiveness comes from the [ ) symbol, tabular figures and to-scale diagrams, not from loud colour or effects. |
Positioning is the place a product claims among the alternatives. fiscalclock's claim rests on three points, each one checkable.
| Point | What it means | Evidence |
|---|---|---|
| Data-defined | A calendar is a JSON definition you supply; the library has no built-in or named calendars. | ADR-0004, README |
| Identical in three languages | One Rust core; the Python and npm packages return its JSON unchanged, and CI requires the raw outputs to match byte for byte. | ADR-0019, README |
| Correctness shown, not claimed | Expected results come from cited sources or independent generators, never from fiscalclock's own output. | PDR goal 3, Testing-Strategy |
Comparisons stay narrow and sourced. Other tools already model week-based calendars (ThreeTen-Extra, Power BI, SAP, Tempo and Perl's Fiscal5253), so fiscalclock does not claim to be the first or the only one. The gap it addresses is narrower: no open-source, data-defined engine gave the same answers in Rust, Python and JavaScript, and a crates.io search for "fiscal" found no 52/53-week or 4-4-5 calendar engine, as of 31 Oct 2026 (PDR, Analysis).
Every fiscalclock period is a half-open interval, written [start, end_exclusive): the start date is included and the end date is not (ADR-0007). Adjacent periods meet exactly, because one period's end_exclusive is the next period's start, and the "plus one day" corrections that cause off-by-one errors disappear; last_day is still given for people who think in last days (ADR-0007). The identity is built on this rule.
-
The symbol is
[ ): a closed square bracket for the included start, and an open parenthesis for the excluded end. See Logo-Guidelines. - The open end carries the accent colour, "because the excluded end is the detail that matters" (Phase 3 sketches).
-
The direction is "C. Interval", chosen by the owner on 1 Nov 2026 from three directions (A. Ledger, B. Period grid, C. Interval), and set in IBM Plex Sans and IBM Plex Mono instead of the Inter and Commit Mono first sketched (DD-013). Plex's figures are tabular by default and its
I,land1are clearly distinct (typography research). See Typography. -
Diagrams carry the idea further: a filled marker for
start, an open marker forend_exclusive, labelled "included" and "excluded" (research brief). See Diagrams-and-Data-Visuals.
| We are | We are not | Basis |
|---|---|---|
| An engine that computes any calendar from your definition | A library of named or built-in calendars | ADR-0004 |
| About fiscal years, quarters, periods and weeks as plain intervals | About holidays, business days, working hours, pay periods or sprints | ADR-0015 |
| Calm, precise and plain | Playful, loud or "blazing fast" | DD-006, AGENTS.md |
| Neutral surfaces with one teal accent | Gradients, glows, shadows or a rainbow of colours | DD-013, DD-019 |
| Evidence first: counts, commands, sources and review dates | Superlatives, logo walls or hero statistics without a citation | trust research |
| Equal in light and dark themes | A light design with a dark mode added later | DD-005 |
Usable by agents through structured errors and explain today, with an MCP server planned for 0.4 |
"AI-powered" or "built for the AI era" | Agents-and-MCP |
| An independent project with its own identity | A variant of the sibling project workclock | DD-001 |
- Design-System, the hub for all design pages
- Voice-and-Writing and Logo-Guidelines, which apply this page
- Design-Decisions: DD-001 to DD-006 and DD-013
- Research brief
- PDR and README
fiscalclock is licensed under MIT OR Apache-2.0 (MIT, Apache-2.0). Last reviewed: 31 Oct 2026. Found an error on this page? Report it with the documentation form.