# Condominium accounts: full write-up

An experimental project by Gildas Frémont, freelance product director (https://gildas.fyi), volunteer member of the owners' council of a condominium in Seine-Saint-Denis, near Paris.
Public page: https://gildas.fyi/en/experimental/copropriete
Status: in use since September 2026. Private tool, password-protected; neither the site nor the repository is public.
Built with Claude Code and Cowork.
French version of this write-up: https://gildas.fyi/experimental/contexte/copropriete.md

This write-up describes the method and how the work unfolded. It deliberately contains no names (building, property manager, co-owners, suppliers), no real amounts and no unit numbers.

A note on terms: in France, a building held in co-ownership (copropriété) is run by a property manager (syndic) and overseen by an owners' council (conseil syndical) of volunteer co-owners.

## The bet

A volunteer owners' council can, on its own, rebuild from the property manager's raw documents a set of accounts that any co-owner can check, and track the actions to take, provided every figure is computed from cited sources, cached and rechecked automatically, and every action is a GitHub issue.

## Context

A change of property manager, and a claim against the former one that needed a figure. The sources available: the general ledger kept by the former manager, and the new manager's document portal. The ledger serves as a benchmark for comparison, never as a source.

## The calculation method (set on October 3, 2026)

For any figure rebuilt from several sources:

1. Input data goes into a CSV, one row per value, with a `source` column (document, page, account, date).
2. The method stays in the code, in a commented `calculer…()` function that says what is subtracted from what and which source wins (52 modules of this kind).
3. The result is cached in a CSV by a script run by hand (8 scripts), with the intermediate values and their sources. The site reads the cache and does not recalculate.
4. A check redoes the calculation and flags a stale cache, with the command to rerun.
5. The site shows the components of the figure, with their sources as a caption.
6. The README describes the files and the regeneration command.

A value inferred by the tool and not signed off by the property manager carries the label "not signed off by the property manager." When documents are missing (contribution notices, for example), values are rebuilt unit by unit, marked "inferred," and every reconstruction decision is recorded in a log.

## The checks

59 numbered rules, rerun on every deployment and every hour, shown on a dedicated page with an alert banner on the home page. They cover duplicate documents, documents from another building, matching, the suspense account, payroll, due dates, compliance with the issue protocol, double-entry consistency, allocation of charges and freshness of the caches. The double-entry books are rebuilt document by document, without taking anything from the property manager's ledger.

## Actions as GitHub issues

- A goals → problems → solutions tree, adopted on September 25, 2026.
- A solution carries an action, a channel, a "done when" criterion and a single status label (to do, waiting on the property manager, waiting on the owners' council, waiting on a third party, blocked).
- The site reads the body of the issues through their headings and a hidden block.
- The GitHub project board is derived from the issues and is never edited by hand.
- As of October 24, 2026: 91 issues (80 open), 19 problems and 66 solutions. Goals: cash 46, compliance 46, recovery 39, building health 30, property value 20 (one issue can serve several). Statuses: to do 39, waiting on the property manager 16, blocked 7, waiting on the owners' council 7, waiting on a third party 2.

## Sharing with the co-owners

A script exports an allowlist of files to a shared repository, and blocks the export if it finds banned terms, paths, email addresses or phone numbers. It can also re-import a contribution while keeping its author. The site itself exists in a single version, behind a password, where only social security numbers and IBANs are masked in search excerpts.

## Timeline

- September 23, 2026: first commit. 1,520 documents logged (metadata, text, OCR), expenses matched to their documents from 2017 to 2026, document-by-document matching of 2023 (91 of 92 lines supported), 2024 (91 of 95), 2025 and 2026.
- September 24: claim file with figures (a 14-page PDF generated by script). Working protocol written. Project board updated every hour by a local agent. A queue of GitHub commands run on the Mac.
- September 25: issues restructured into a tree, command queue dropped, first version of the Next.js site.
- September 26: visual system, automatic export of the issues to the site.
- September 28–29: water and meters per unit, suppliers, quotes, insurance linked to claims, the co-ownership rules compared with the cost allocation keys.
- October 1: proper names leave the code and move into the data.
- October 2: cash flow page (age of unpaid charges, invoices to pay), "Petty cash" section removed. Work starts in parallel in several worktrees merged by pull request.
- October 3: the six-step calculation method.
- October 4–6: cash reworked (called, received, gap per budget envelope).
- October 7: a 58-commit day. Finding: the water allocated by the former property manager matches the water utility's invoices over 2017–2025.
- October 19–20: repository shared with the co-owners, calendar exported as .ics, protocol cleared of what was not practiced.
- October 21: latest commit to date.

## Trial and error

- A queue of GitHub commands left by the conversations and run by a script on the Mac: set up on September 24, dropped on the 25th. The conversations run git and gh directly.
- Flat issues: restructured into a tree on September 25.
- A "control tower" conversation in charge of monitoring progress, and a mirror of the notes in a Claude project: removed on October 20; the checks page shows what is late.
- A version of the site reserved for the owners' council, with names masked: dropped in favor of a single version.
- "Petty cash" section: removed on October 2, its pages moved elsewhere.

## What came out of it

A read-only site, 15 knowledge notes, about a hundred accounting files, 20 letters, a claim file, 8 work-site notes, a general meeting file, a calendar and a shared repository.

## Numbers

- 433 commits from September 23 to October 21, 2026, over 17 active days, 129 of them signed by Claude.
- About 22,500 lines of TypeScript.
- Stack: Next.js 16, React 19, TypeScript, Python scripts, tesseract, GitHub Actions, launchd, Vercel.

## Principles

- A fact goes in a note, an action goes in an issue.
- The former property manager's ledger is a benchmark, never a source.
- An inferred value carries the label "not signed off by the property manager"; every reconstruction decision is recorded.
- The site recalculates nothing: it reads caches that a check verifies.
- The project board is derived from the issues; milestones are only used for real deadlines.
- The site is read-only; actions live in GitHub.

## Data model (simplified)

Document (type, date, heading); Expense (envelope, supplier, fiscal year, amount, documents, status supported or undocumented); Envelope (type operating, works or fund, fiscal year, vote, decision, called, collected, spent); Contribution call (unit, envelope, allocation key, share, source); Unit (number, ownership shares, account, water readings, changes of ownership); Bank movement (statement, page, date, in, out, documents, expenses); Double-entry record (journal, lines, documents, matching); General meeting decision (issue, execution state, subject); Problem and Solution, read from the GitHub issues (resolved when, goals; what we do, channel, done when, blocked by, status). Also: invoice, payment, supplier, contract, quote, work site, insurance claim, common area, exchange thread.

## Places on the site (breadboard)

Cash, Envelopes, Expense (with the document in a side panel), Charges by theme, Contribution calls (with an allocation key simulator), To handle (subjects, quotes, invoices to match, insurance claims), General meeting, Calendar (.ics export), Units, Suppliers, Documents, Checks (including double entry), global search.

## Anecdotes

- On October 7, 2026, a 58-commit day, the tool established that the water allocated by the former property manager matched the water utility's invoices exactly over 2017–2025.
