メインコンテンツへスキップ

メンテナンスボード

本文は英語の原文で表示しています。

ガイドメンテナンスボード11/13

Open Analysis in the left rail. It reads the same ontology folder as the Map. The example is labeled; its source code has not been checked by this screen.

Start with the selected responsibility pair and its visible comparison rail. The central graph expands that pair into actual capability or other concept endpoints. Each directed arrow is one recorded dependency declaration. A thicker highlight identifies selection, not volume, risk or runtime traffic. Choose a named pair, an exact declaration control, or an endpoint's first shown declaration.

The selected declaration opens its exact endpoints, structured relationship note and declaring document beside the graph. A missing relation-note field does not establish that the Markdown body lacks an explanation. Open the declaring document reads the original record and retains a return to the selected claim.

Inspect the implementation claim continues from a dependency to the source capability. Evidence to check also opens named capabilities directly. It separates a documented implementation role, a recorded source path, missing explanation and unknown source currentness. A missing path means the path was not recorded; it does not prove that the code is absent. Review and correct this claim opens the existing Map editor for a local documented concept.

A scope with no cross-responsibility dependency declarations still shows its recorded capability evidence. It does not present an empty dependency record as proof that the system has no dependencies. Use the visible remainder controls to inspect additional pairs or capabilities without panning a map.

The other section tabs retain Review summary, Wiki, Guidance and Written explanations. Their facts belong to those records. An agent request remains inspectable and unsent until you send it; changing sections preserves the draft. The old census and maintenance tab board is no longer a second destination behind Analysis. Existing bookmarks enter the corresponding relationship, evidence or record question. For graph maintenance commands, see the CLI guide.