Repository docs: architecture and repo learnings

Starko AI remembers what it learns about your codebase, and it keeps that memory where your team can read and correct it: in the Knowledge Hub, under Repository.

kh repository

The Repository page

Each project with a linked repository has a row with two documents:

Architecture is a map of the repository: what the product is, how the code is laid out, which commands run fast checks, conventions, where things live and the gotchas the agent hit. Starko AI writes it when you press Learn project in the project's settings, and refreshes it on request.

Repo learnings are the small facts Starko AI discovers during runs ("the e2e suite needs the dev server on port 3000 first"). Each is filed as a ticket tagged repo-learnings in the project's backlog, and the condensed version is published here.

The status chips show whether each document is not started, a draft or a published version.

Why this matters

Every Starko AI run starts with a summary of the architecture doc and the open learnings for its project, and it can read the full documents on demand. A good architecture doc is the difference between a run that spends ten minutes finding the checkout code and one that goes straight to the fix.

Editing and publishing

Open a document to read it as an article. Your team can edit any section and publish a new version; agents read only the published version. Put rules in the project's Agent instructions instead; the architecture doc is for descriptions.

Curating repo learnings

Learnings are tickets, so you curate them like a backlog:

Edit a learning to correct it.

Close or cancel it to retire it.

Promote an important one to agent instructions if it is really a rule.

Press Condense on the Repository page to have Starko AI merge overlapping learnings into one document and preview the result before publishing.

Refreshing

Refresh the architecture doc after a significant restructuring or every month or so. Learning a project is billed like a fix run.

Did this answer your question?