Keep a holiday calendar right prototype

Three questions the journey judgement left to the prototype:

1. Where do the two own actions stand? The owner decided that Rebuild business days moves from the tab to the header, beside Derive a calendar (RS-PAGE-03). The prototype draws both there and turns the rebuild into an operation dialog, so the header holds buttons and the tab holds the view.
2. How is the Business days view drawn? No rule of the standard draws a derived, read-only view. The prototype defines one, below, for the standard to take.
3. What does a reader see? A person who may not write sees the mark Read only and no action, on the page and in every panel (RS-FEEDBACK-01, RS-FEEDBACK-02).
4. Where does a reference lead? The country of a calendar is a link to the country's page with its flag, on the list and on the Details (RS-PAGE-08, ES-REF-01); the calendar type is a link to its classification page.

• The list. Breadcrumb, plural title and one sentence (RS-LIST-01); Refresh with its load time, then Add, at the right (RS-LIST-03, ES-REFRESH-06, ES-REFRESH-16); a search box with Clear (RS-LIST-04); sortable columns Code, Name, Calendar type, Country, and Holidays from, which says in words what the calendar is made of; the pager with the count first and 15 rows (RS-LIST-17); search, page, size and order in the address (RS-LIST-20); the code and the country in monospace with their flags (RS-ICON-03); a click on a row opens the page (RS-LIST-10). The nothing-matches state offers Clear the search (RS-LIST-21).
• The record page. The breadcrumb ends at the code and the title is the name with the flag (RS-PAGE-01); the lead reads code and version (RS-PAGE-02); the actions stand in this order: Refresh with its load time, the access mark, Derive a calendar, Rebuild business days, Edit, Delete (RS-PAGE-03, RS-FEEDBACK-02). A QuantLib calendar is read only, so it draws Derive and nothing else, and its Details end in the notice that says why (RS-WRITE-33). The tabs follow the shape: Details, Rules, Exceptions, Diary events, Business days, History; a tab that does not apply is not drawn (RS-PAGE-09). The details stand in four columns in the field table's order, with the fixed reason under the code, the country as a link to its page with its flag, and Holidays from as a link to the base (RS-PAGE-05, RS-PAGE-06, RS-PAGE-08, ES-REF-01); the last-changed line ends them (RS-PAGE-10).
• The parts. Rules, exceptions and events are parts panels: the columns the kind declares, History, Edit and Delete on each row, Add under the table (RS-RELATED-04, RS-RELATED-05); each opens the record dialog with the parent given, the history in a wide dialog, or the remove dialog (RS-RELATED-06). A rule is shown in words, "Last Monday of May", because a rule has no name (the journey's gap 6). The rule dialog's fields follow the kind (RS-WRITE-07).
• The dialogs. Edit is titled Edit and the page's title, and says under its title when the record was loaded (RS-WRITE-20, RS-WRITE-16); the key is fixed with its reason (RS-WRITE-03, ES-PAGE-08); the fields stand in two columns in the field table's order (RS-WRITE-11); one line of help stands under a control (RS-WRITE-12); Why and Commentary close the form (ES-EDIT-02); the footer holds Cancel then Save, each with its icon, and no Delete (RS-WRITE-14); a create states its reason in a note and lists what is still to fill (RS-WRITE-17, RS-WRITE-13); the ✕ and Cancel alike close at once while nothing changed, and ask You have unsaved changes. Close anyway? once a field has, in every dialog (RS-WRITE-24). Delete confirms, names the record, says what is lost and asks for a reason (RS-WRITE-25, RS-WRITE-30).
• Derive a calendar. The record dialog titled Derive a calendar from <name>, with the base shown as a fixed field and the type and the country given from the base; a create, so no reason (RS-WRITE-17). After it the screen opens the new calendar (RS-WRITE-19).
• Rebuild business days. An operation dialog: one field, Build up to the end of, the note that a rebuild adds the days not built yet, and the button Rebuild. The reply is a notice with the count of days written. This is the one dialog that is not a record, remove or revert dialog, and the standard's RS-WRITE-31 gains the operation dialog as a fourth shared shape, or names the exception.
• History. The shared timeline of the Entity screen specification: the event chart with one bar per day split by kind and a legend with counts (ES-HIST-01 to 06); then the rail, newest first, under a day divider, with the time and the current-version emblem in the left gutter (ES-HIST-11); one line per entry with the kind, the record and its version, the reason, the author and the fields that changed (ES-HIST-07); the note on its own line (ES-HIST-08); the detail collapsed, a table of what was and what is now, or the whole record for a first version (ES-HIST-09); No changes for a version that moved no field (ES-HIST-10); Hide system activity at the top right (ES-HIST-13 to 18); Revert on every version but the current one, for a writer (RS-HIST-02); and, for a QuantLib calendar, the box What this history cannot show (ES-HIST-39). A part's history is the same rail in a wide dialog (RS-RELATED-06). The first draft of this prototype copied the two-pane compare of the live reference data screens and of the classifications prototype; the owner caught it on 2026-10-25, both sources are marked legacy, and this page carries the timeline.

The rule the standard gains, in words. A derived view is a tab of the record page that shows what the record's parts produce. It is read only and has no Add. It:

• names the period it shows and lets the person step it, here a year with Previous and Next, and keeps the period in the address;
• shows one block per natural division, here one per month, in the same grid the details use: three across, then two, then one;
• shows each entry with its date, its words and what produced it: a rule, an exception, the base, in a faint column at the right, so the person reads cause beside effect;
• draws a business day an exception opened in green, because it is the one entry that adds a day rather than takes one;
• offers one comparison, Compare with, and draws the other calendar's holidays in italics with the words Holiday in <code> only, because the union is the definition a pair settles on;
• says in one line what it does not show: a change to a rule or an exception shows once the year is rebuilt;

• has an empty state that names the action: /No business days are built for

  1. Rebuild the calendar to build them/, with the link for a writer and

  the words for a reader.

The three user calendars and everything under them. The history of Acme.Desk. The QuantLib holidays of the bases, typed in for 2026 only. The count of days a rebuild writes. The flags, which are the country code in a box. Nothing is written: Save, Add, Rebuild and Delete show a notice and go back.

index.html is the shell, prototype.css the look from the web app's tokens, and prototype.js the data, the rule engine that turns rules into dates, and the screens. The query string is the state; every link changes it.

Open. The owner signs it off before the build task starts. The build then moves the web's calendars screen to this: Rebuild into the header as an operation dialog, Refresh and the load time on the page, the dialog titles and load times, the Business days view as drawn here, and the Read only mark.

• The rebuild that rewrites a built day, and the QuantLib holidays the server does not read: the view draws the intended screen, and the journey's gaps 1 and 2 carry the server work.
• The ORE export, which has no screen until the server returns the document.
• The role below the tenant administrator; the reader here is any person who may not write.