decision

No definition

The passages, in corpus order

28 files.

MeetingContract import scope review3

  • 42:17Then the decision of this session: a purpose-built contract viewer, an island rendered from a json fragment of the contract, loaded on demand, under the page bu…
  • 42:17…built contract viewer, an island rendered from a json fragment of the contract, loaded on demand, under the page budget. Participant-3 writes the decision note.
1 other passage
  • 45:12I will, under the publication decisions. And the schemas become candidate objects, as Participant-2 said, so the to-do page lists them.

MeetingTwin resources review1

  • 57:55Decision of the session, then: minhash for twin resources, as Participant-2 described it, with the exact index recomputed on the close pairs. Participant-4 revi…

MeetingTheme override model3

  • p. 65 · DECISION Slots, islands and layers Named slots with typed view models. Islands for the interactive parts, content reachable without JavaScript. A budget…
  • slide 65 · DECISION Slots, islands and layers Named slots with typed view models. Islands for the interactive parts, content reachable without JavaScript. A budget…
1 other passage
  • 48:45Slide six, the decision. Slots, islands and layers: named slots with typed view models, islands for the interactive parts only, and cascade layers so that the p…

TermQuery1

  • line 6…at the model knows about it, where it is used, what it is linked to and the decisions that touched it, or answers a question of the whole corpus, in a compact t…

TermSection mention1

  • line 7…ed by it, a rule under ## Rules constrains it, a note under ## Affects of a decision is affected by it. The section decides the relation, so the link is typed o…

TermLock2

  • line 6…e.lock.yaml, named by the lock key of the configuration, that records human decisions: accepted and rejected links, merged and separated twin resources, rejecte…
  • line 6…declaration files it already. The links are recorded, not read. The build log counts the decisions applied. Nothing is ever written into a knowledge repository.
Show the 20 other files

TermMeeting2

  • line 6… a note typed meeting: its minutes, with the date, the participants and the decision the session produced under decisions, the transcript of what was said and, …
  • line 6… not concepts: it enters the model through the pages it mentions and through the decision someone wrote as a note of its own, which the page names in a callout.

TermNote1

  • line 7…s a typed entity: a screen, a rule, a business object, an API, a process, a decision, a term. A note has a page made of its rendered markdown first, at most fiv…

TermPrivacy1

  • line 6…_transcripts, false by default, so that a transcript is indexed only when a decision asks for it. The configuration never carries a credential either: a private…

TermType cascade1

  • line 6…xtension, frontmatter key), then the note's own frontmatter. The most specific wins, and the origin of the decision is kept on the entity and shown in the site.

TermType1

  • line 6…es: a screen, a rule, a business object, an API, an operation, a process, a decision, a term, a document among others, each with a label per locale, a glyph, a …

TermBuild log1

  • line 6…hod, keyword pages and expressions under the threshold, twin resources, the decisions of the lock applied, findings per severity and per check, the contracts im…

DecisionLock file for human decisions3

  • line 8…chema and stops on a missing or invalid one, as on a configuration error: a decision is never dropped in silence. The keyword discovery honours rejected_terms, …
  • line 8… version, and the configuration validator says so. The build log counts the decisions applied. Nothing is ever written into a knowledge repository, and a decisi…
1 other passage
  • line 8…the decisions applied. Nothing is ever written into a knowledge repository, and a decision lives next to the configuration, versioned, reviewed like any change.

DecisionGPL-3.0-or-later1

  • line 8…cence is outside the allow-list fails the check, and widening the list is a decision of the maintainers. The wiki a project generates with the tool is the proje…

Business objectCandidate1

  • line 6…a pair of resources scored as twins without reaching the merge threshold. A decision on a candidate goes to the lock file of the configuration repository, never…

Business objectEntity1

  • line 6…identifier derived from its source and path, a type with the origin of that decision, a title, aliases, an application, a domain, a locale, its declared attribu…

Business objectBuild1

  • line 6…and the expressions under the threshold, the twin resources reconciled, the decisions of the lock file applied, the domains the neighbourhood suggests with thei…

ProcessBuild pipeline1

  • line 28Write the model and the build log, the decisions of the lock file counted in its summary and the suggested domains listed with their pivots, then one fragment p…

ProcessQuery2

  • line 7…sed with file and line, what it is linked to and how sure the model is, the decisions and sessions among those links. The same command runs the search of the si…
  • line 13… hold them, its links with relation, direction, confidence and methods, the decisions and sessions among them; or walk the links to another note, to what lies w…

ProcessRelease2

  • line 7…and says so, a patch never does. The release guide is the contract; the one decision that stays human is the merge of the version pull request, and the publicat…
  • line 13The maintainer reads the version pull request and merges it: this is the decision to release.

RoleAuthor1

  • line 6…son who writes notes in a knowledge repository: a screen, a rule, a term, a decision, in standard markdown with the frontmatter that qualifies it and the links …

ScreenDecision page18

  • line 8The page of an architecture decision: short, dated, with its consequences. Same shell as the entity page: the tree of the space on the left, the title and the p…
  • line 8…here a reader expects them. A reader comes to check two things, whether the decision holds and since when, and finds them at the head of the panel; the rest of …
16 other passages
  • line 8…es to check two things, whether the decision holds and since when, and finds them at the head of the panel; the rest of the page says what the decision changed.
  • line 10A decision affects pages without being affected by them: its relations are almost all written, since a decision cites what it changes, and the page lists them a…
  • line 10…ion affects pages without being affected by them: its relations are almost all written, since a decision cites what it changes, and the page lists them as such.
  • line 14… › 2026 › title". Under the title, one chip reads the type and the status, "Decision · accepted", the status worded when it is one of the three the profile decl…
  • line 14…pt as written otherwise; then the identifier of the note and the day of the decision, from its date attribute, each left out when the note has none. Nothing els…
  • line 16…n, section by section, the three sections the convention asks for, context, decision and consequences, coming from the file itself. Under the note, one callout …
  • line 16… file itself. Under the note, one callout per session the model ties to the decision at either end of a link, the decisions reference of a meeting, a written li…
  • line 16…r end of a link, the decisions reference of a meeting, a written link, or a decision whose note names the meeting: "Decided in session on 12 March. The exact pa…
  • line 16…ink leading to the last cue of the transcript of the meeting that names the decision, at the timecode the sentence quotes, or to the page of the meeting when no…
  • line 18The right panel opens on the properties of the decision, the status and the date first, the two things a reader comes to verify; then "Supersedes" and "Supersed…
  • line 18… from the supersedes links of the model at either end, so that a superseded decision names the one that replaces it and the replacing one names the one it repla…
  • line 18…wn. The related pages are the mentions panel built from the passages of the decision itself, the pages its text cites, with the pages that cite it, most passage…
  • line 18…es, with the pages that cite it, most passages first, under the note that a decision affects pages without being affected by them: its relations are almost all …
  • line 26Open the minutes → meeting page, at the cue that names the decision
  • line 27Open the decision it supersedes, or the one that supersedes it → decision page
  • line 27Open the decision it supersedes, or the one that supersedes it → decision page

ScreenEntity page1

  • line 17… the entity page, the meeting page, the document page, the API page and the decision page: the line counting them and naming what grouped them, "3 files grouped…

ScreenMeeting page10

  • line 8…ge puts the note, the three files stand as tabs; what the meeting produced, a decision written elsewhere, is named in a callout rather than mixed into the text.
  • line 10…ng brings passages, not concepts: it enters the model only through the pages it cites and the decisions someone took the trouble to write as notes of their own.
8 other passages
  • line 16…h 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 to the meet…
  • line 16… panel cites. The callout "Decision taken here" stands under the last cue a decision the model ties to the meeting was recognised in, the decisions no cue names…
  • line 16…he last cue a decision the model ties to the meeting was recognised in, the decisions no cue names at the head of the transcript; the model ties a decision to t…
  • line 16… 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, the decisions reference of the note…
  • line 16…er end of a link, the decisions reference of the note, a written link, or a decision whose note names the meeting, and the callout is absent when nothing links …
  • line 18After 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.
  • line 20…hat 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 fo…
  • line 29Open the decision → entity page

ScreenSpaces1

  • line 13… without it, the labels of the dominant types of the space ("Business rule, Decision, Screen"); its page count; and the date of its newest change from the git h…

ScreenContract viewer1

  • line 18…d the only fetch of the whole site is the one of the view, once per page. The decision purpose-built contract viewer says why no third-party viewer is embedded.

What we know

Occurrences
62
Files
28
Spaces
Briefs, Glossary, Specifications

No declared property: there is no file for this word.

Maybe the same thing

Expressions close in form and context. A lead, not a claim.

See the neighbourhood map6 pages6Neighbourhood mapdecision

Neighbourhood map decision

Distance1 hop

Types
existing pageword without a note

50 neighbours in total, more than the map shows.

The 6 neighbourstextual equivalent

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