AI Driven SDLC
Login

AI Driven SDLC Documentation

Guides, references, and best practices for the AI Driven SDLC platform.

Workspace context

How the ready repositories fit together

Workspace context

Workspace context is separate from any single repository wiki. Open Engineering Context Graph, then Workspace, or go to /code-chat/knowledge.

Refresh reads the wikis that are already ready. It does not rebuild those indexes.

Picture

The picture has four parts:

Section What it shows
Picture The map, the groups, and short findings
Roles What each repository is, in a full sentence
Connections Links that name a package, an API, or a file
Gaps What the wikis still do not explain

A shared contract group means two or more repositories mention the same package. The line on the map states that reason in full. Hover any shortened label to read the rest.

Similar names are kept apart from those connections. The same filename, or an unnamed generated id that appears in two files, is listed with both repositories and the evidence. The text says it is not a proven call.

Roles

Each ready repository gets a role and a rationale taken from its wiki:

  • A repository whose wiki describes APIs, storage, and workers is a backend service.
  • A repository named as the workspace, and whose pages describe guidance and orchestration rather than the product application, is workspace tooling.
  • A test framework kept beside the product repositories is called out as a sample or external product, with the sentence that says what the framework is.
  • A separate product, such as a visualization application, keeps that description in the rationale even when its role chip is broad.

The rationale is clipped on a word boundary. It does not stop mid-word.

Written pages

The written workspace pages are the text another model should read:

  • Workspace context: the repositories, the groups, and the connections
  • Workspace insights: findings, roles, connections, and similar names
  • Cross-repo map: the same split, with the reason for each row
  • Shared concepts: identifiers that show up in more than one wiki

Internal names are written in plain language. A connection row says Shared contract or Documented relationship, and a confidence of Likely or Needs check.

Download

Download offers:

  • Markdown: the written workspace pages, with GitHub links where the repository has a GitHub address
  • Knowledge bundle: the same pages in a bundle another model can read, without private in-app addresses

Use the download when you want an outside model to see which repositories exist, what each one is, and which package or file actually ties two of them together. Similar names are included so the model can see them, and they are labeled as not a proven call.