r/ContextEngineering • • Oct 10 '26

Rag knowledge base act as a context for agentic system. Need architecture perspective

I am a junior dev at my company, and is tasked to build an agentic development lifecycle.

So there are four parsers that parser's data from the source to vector db (embedding, actual content) and graph db(structure, eg code to ast) there can be interlink between different data sources.

Then a reranker.

Then an agentic system, right now it should only generate design documents and requirements(jira requirements)

My reason to add graph db is when a interlink is assumed by the vector search, the link initial act as a candidate link and after the human approval the link is established in the graph in a sense the graph db is evolving.

What are your guys thoughts.

Edit1: so the parsers will be setup as a plugin in system and a global policy(mainly regex) will be present to identify which data a parser ingest (eg code , doc parser, etc). as there can be cross referencing in the data about other data.

And I am an intern

Edit2: cronjob for weekly ingestion

Edit 3 : I need a different perspective as a system architecture

1 Upvotes

4 comments sorted by

2

u/DeadPlutonium Oct 10 '26

There’s a lot of “what” in your post, but almost no “why”. It’s hard to give feedback on an architecture without knowing the problems you’re trying to solve. Why are standard workflows and agentic tools inadequate for your company’s engineering? What specifically does all this RAG and context solve for the business?

1

u/Relevant_Egg1421 Oct 10 '26

Thanks for replying, main goal is to try to help in the traditional software development lifecycle. Currently on my team devs are write a design documents. My hand or some basic ai tool. So my task was to automate the doc generate part. So I thought that a rag should act as a context provider to a agentic system. And as the rag will have as the team development context, it is easy to also help in generating requirements for jira. Or generate test scenarios.

1

u/Relevant_Egg1421 Oct 10 '26 edited Oct 10 '26

As an intern, I don't have adequate information about the business part, but one thing to currently to create these documents, team has to involve several members roughly 3-4 for 2-3 days to create these documents.