Meeting page

ScreenSpace Specifications

The page of a working session (note: Meeting) that exists as a note (note: Note), a transcript (note: Transcript) and a deck (note: Deck), read as one page. Same shell as the entity page: the tree of the space (note: Space) on the left, the title and the panel where a reader (3 passages, no note) expects them. Where the entity page puts the note, the three files stand as tabs (33 passages, no note); what the meeting produced, a decision (62 passages, no note) written elsewhere, is named in a callout (7 passages, no note) rather than mixed into the text.

A meeting brings passages (note: Passage), not concepts (3 passages, no note): it enters the model (note: Model) only through the pages it cites (31 passages, no note) and the decisions someone took the trouble to write as notes of their own.

Today

The page stands on the shell of the entity page. When every note of the space (5 passages, no note) carries a date (44 passages, no note), a date attribute (note: Attribute) or a file name that starts with one, the tree (47 passages, no note) on the left groups (23 passages, no note) the notes by year and month, newest first, each counting its notes, the year and the month of the page open and the page marked; a space with an undated (3 passages, no note) note keeps its folder tree. The breadcrumb (3 passages, no note) reads "space › March (3 passages, no note) 2026 › title". Under the title, a line names the type (note: Type), the duration (3 passages, no note), from the duration attribute of the note or the timecode (note: Cue) of the last cue of the transcript, "1 h 12", and the participants (14 passages, no note): "Pseudonymised participants" when the configuration (note: Configuration) enables pseudonymisation (note: Pseudonymisation), else how many the note declares.

The representations (note: Representation) follow as the tabs "Transcript", "Notes" and "Deck", one per file the build (note: Build) grouped into the page: the transcript, the notes, the deck or another converted document (note: Document), with the mention (note: Mention) "Grouped automatically" at the end of the row (41 passages, no note) when the twin-resource reconciliation merged them. A deck and the PDF preview (note: Preview) kept next to it are one representation: the "Deck" tab offers the original to download (30 passages, no note), the preview in the document viewer, opened as soon as the tab is shown, and the extracted text (note: Extracted text), once. The tabs follow the tablist pattern (3 passages, no note) the accessibility rule asks for, served as anchors (3 passages, no note): without any script (37 passages, no note) the page shows one panel (97 passages, no note) at a time, the panel of the tab followed, the one holding the position (23 passages, no note) a citation lands on, else the first, and a browser (31 passages, no note) without the selector (4 passages, no note) the stylesheet (26 passages, no note) relies on shows them one under the other; once its script runs, the selected state (36 passages, no note) follows the panel shown, the arrow (3 passages, no note) keys (46 passages, no note) move along the row, a tab followed updates (3 passages, no note) the address (56 passages, no note) without scrolling and a citation landing inside a panel shows that panel. The transcript reads as timestamped lines, "12:04 Participant-1 — …", the speaker of every cue carried from the transcript reader (note: Reader) and pseudonymised with the text, each timecode an anchor at the position the mentions panel cites. The callout "Decision taken here" stands under the last cue a decision the model ties (3 passages, no note) to the meeting was recognised (37 passages, no note) in, the decisions no cue names at the head of the transcript; the model ties a decision to the meeting at either end of a link (note: Link), the decisions reference (30 passages, no note) of the note, a written link (note: Link), or a decision whose note names the meeting, and the callout is absent when nothing links them. The file to download follows the lines and, when pseudonymisation applied, the note that the names are replaced at publication (40 passages, no note) by stable pseudonyms (3 passages, no note) and that the mapping is never published. The notes are rendered (33 passages, no note) as on the entity page, with the legend of written links and recognised words (note: Recognised word).

After the tabs, the path of every file follows, with the edit link of the note; a meeting without a transcript keeps the callout of its decisions there.

The right panel lists the properties of the meeting, the date, the duration, the space linking to the file tree of the home, then the grouped files, said as every template (22 passages, no note) says them, "3 files grouped — same base (19 passages, no note) name", each file with its kind and "Separate these files", with, under them, why the build grouped them, read from the pairs (47 passages, no note) the reconciliation scored, "3 files: same folder, same base name, same commit (29 passages, no note), high textual overlap.", absent when the model recorded none. The related pages (note: Related page) are the mentions panel built from the passages of the meeting itself, the pages its minutes, its transcript and its deck evoke, most passages first, each excerpt (4 passages, no note) leading to the cue or the line on this page, with the pages that cite the meeting, under the note that a meeting does not enter the model: it brings passages, and sometimes a decision someone took the trouble to write elsewhere. Last, the neighbourhood map folded behind its line.

Objects

Actions

  1. Follow a tab → the panel of that representation
  2. Open the decision → entity page
  3. Open a related page → entity page
  4. Download a file → the original file

Rules

Properties5

Application
Generated site
Status
valid
Roles
Reader
URL pattern
/{source}/{path}

5 declared keys. The rest of the file is free text.

On this page4

  1. Today
  2. Objects
  3. Actions
  4. Rules
See the neighbourhood map6 pages6Neighbourhood mapMeeting page

Neighbourhood map Meeting page

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

75 neighbours in total, more than the map shows.

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.