anthemionanthemion-syngraphe
← all of Classical

Classical

The syngraphe

The written specification for a public building — materials, dimensions, sums — cut into stone and set up where anyone could check it.

Athens inscribed its building accounts in public for a reason, and it is the mechanic here: a public account exists to be checked. Every figure is cut as a groove under its own number, scaled against the largest in the column, and the total carries two — the stated total as a dashed outline, the true sum as a bar cut from the same edge. When they agree the sum fills the outline exactly; when they do not, it runs past the line the account claims for itself and you can see the error without reading a digit. The whole thing sits in a generated entablature: a crown of dentils, an Ionic kymation of eggs and darts, and the astragal beneath it, over a field grouped every fifth line. The mouldings are cut to fit rather than tiled — the run is divided into a whole number of units and each is cut a little wider or narrower so the course comes out whole at both ends, which is what a mason does and what tiling cannot do. The carving is on the crown only, and the frame descends a ladder as the column narrows: kymation, then astragal, then a plain rule.

ElementArea
Living96 m²
Sleeping124 m²
Workshop84 m²
Circulation62 m²
Plant18 m²
Store28 m²
Total384 m²

Integration

<link rel="stylesheet" href="anthemion.css">
<script type="module" src="anthemion.js"></script>

<anthemion-syngraphe rule="fifth" frame="on" bars="on">
  <table><thead><tr><th>Element</th><th>Area</th></tr></thead><tbody><tr><td>Living</td><td>96 m²</td></tr><tr><td>Sleeping</td><td>124 m²</td></tr></tbody><tfoot><tr><th>Total</th><td>220 m²</td></tr></tfoot></table>
</anthemion-syngraphe>

Slot

A schedule of areas, a specification, a fee or cost breakdown.

Custom properties

  • --syngraphe-ground

Budget

  • Two per page at most. A page of tables is a report, not a project.
  • Give it a total. Without a <tfoot> there is nothing to audit and it is only a well-ruled table.
  • Do not hand-write the total to match. The point is that the component catches the row somebody deleted.
  • Never ship with `flag`. The grooves already show a mismatch to anyone looking; `flag` prints the two numbers in words, which is the component telling the buyer's client what the buyer got wrong.
  • Set `bars=off` for a column of dates or reference numbers. A bar chart of years is nonsense drawn convincingly.
  • One framed table per page is plenty. The entablature is the loudest thing the drop puts on a page of prose, and two of them turn a project page into a museum label.
  • `frame=off` for a table inside another framed thing. Two orders inside one another is a mistake no building makes.

Restraint is the aesthetic, and it does not survive being applied generously. These limits are the specification, not advice.

Also in structure