Loading Methodology for All Projects
This guide is for heads of project management offices and program managers: how to bring your organization's project management methodology into the system so the agents of every project work by your standards instead of generic frameworks.
The methodology lives in the global corpus — the third (organizational) tier of the knowledge base; see Working with the document base.
What the global corpus is for
| Tier | What lives there | Who maintains it |
|---|---|---|
| Session | Materials of the current conversation: drafts, attached files | Conversation participants |
| Project | Project documents: charter, scope, requirements, plans | The project team |
| Global | Methodology, standards, templates, policies — common to all projects | PMO Manager |
The difference from a shared drive: the global corpus is not a folder someone has to remember to open. It is an indexed knowledge base that the agents of every user and every project consult when answering questions about methodology, standards, and processes. The methodology becomes part of the agent's working environment, not a link in the wiki.
Who can upload
The product has two roles:
- User — works with their own projects and materials. The global corpus section is not visible to them, but the agents they use do work with the methodology.
- PMO Manager — manages the global knowledge base: adds and removes methodology documents.
Users are provisioned from the corporate directory (SSO: SAML, OpenID Connect; LDAP / Active Directory); host administration is granted with an admin flag. If you do not have the role yet — contact your system administrator.
How to upload
- Open the context pane. It has three sections: the current conversation, project documents, and the global corpus — "Global", with a document counter and a lock.
- Unlock the editing mode. By default the global corpus is read-only (the lock badge). Click the lock next to "Global context" (or the document counter) — the section switches to editing mode.
- Add files. Upload the methodology documents: PDF, DOCX, Markdown. The system parses each document — text, tables, structure — and converts it to a model-ready form.
- Wait for indexing. After the upload the corpus is indexed: status badges (indexing / ready) are shown next to the section and the documents. If indexing ends in an error, a reindex button appears.
- Lock again. When you are done, click the lock — the section returns to read-only.
Removing an outdated document is done in the same editing mode.
After the upload, the corpus is automatically linked to all projects (and to new accounts when they are created) — no per-project configuration is needed.
What to put into the methodology base
| What goes in | Examples |
|---|---|
| Methodology standards | Phases and gate controls, roles and RACI, approval processes, terminology |
| Project document templates | Charter, scope, status report |
| Glossary | Corporate terminology, abbreviations |
| Policies | Information security, compliance, document management |
| Frameworks | PMBOK, PRINCE2, SAFe — if the organization works by them |
Do not put into the global corpus: data of specific projects (that is the project tier), personal information, drafts.
An important rule: the agent prioritizes verified project facts (the tracker, project documents) over the methodology. The methodology tells the agent how to work — which phases, which documents, which terms — but it does not replace the project's actual data.
How the agent uses the methodology
- The global corpus is a separate knowledge base next to the project one: when you ask questions about standards, terms, and processes, the agent answers from your documents and cites the source.
- The methodology works for every user in the organization: users who do not see the global corpus section still receive answers grounded in it.
- The documents the agent creates and its methodology answers are based on the uploaded standards — check on your very first project: ask the agent about a phase or a term and look at the citation in the sources.
How to maintain the base
- A standard was updated — replace the file in editing mode; the corpus is re-indexed.
- A standard was retired — remove the document in editing mode.
- State — the status badges on the "Global context" section (ready / indexing / error) — the same ones as on the project section.
Where to continue
- Working with the document base — the project tier: upload, promote, search.
- Project documents: creation and maintenance — the living documents of the project tier.
- Knowledge library — how the knowledge base works overall.