The Orchestration Engine
How the application agentic engine plans, calls tools, and writes across every stage of your MBA application.
The orchestration engine is the core of Admit Architect: an agentic platform that runs a continuous Ingest, Interrogate, Synthesize, Draft, Orchestrate, Submit loop across your entire MBA application.
Most admissions tools are point solutions. A resume reviewer. An essay grader. A chatbot. Admit Architect is different. It is an admissions operating system where every stage of your candidacy is connected to every other, and an agent named Archer plans and executes multi-step work across all of them.
The six stages
1. Ingest
The engine pulls in raw material: your resume, transcripts, test scores, demographic facts, and anything else you attach. Files are parsed into structured text. Every extracted claim becomes a Fact in your Profile Memory, linked back to an Evidence Span inside the source document.
2. Interrogate
The engine runs the Narrative Spine Interview, an 8-question structured conversation that asks about origin, arc, leadership, values, goals, why MBA, why now, and why school. Each answer is evaluated in real time for introspection depth, and the engine surfaces targeted follow-ups rather than accepting surface-level responses.
3. Synthesize
Once the interview has enough signal, the engine synthesizes a Dean Brief: a narrative diagnostic with rubric scores, per-dimension feedback, evidence links, and prioritized next actions. The brief is append-only versioned, so every refinement over time is traceable.
4. Draft
With your spine in hand, the engine drafts essays in the Essay Workbench. Each draft is grounded in the spine, pulls from evidence, and respects school-specific prompts and word limits. You can ask Archer for suggestions, alternate angles, or outright rewrites on demand.
5. Orchestrate
The engine manages the parts of an application that are not essays: Deadlines, Recommenders, and Connections. It flags at-risk work, chases recommender invitations, and drafts school-specific outreach to alumni and current students.
6. Submit
When a school application is complete, the engine validates it against the school template, confirms every component is present, and hands it off to you for final review. After submission, it continues monitoring status and feeds any new information back into the loop for your next school.
What makes it agentic
Three things distinguish the engine from a conventional chatbot or point tool.
Multi-step planning. Archer does not just answer a question. It can read your spine, load a school template, diff your current draft against that template, and propose a concrete edit, all in one turn. Every action is an explicit tool call the engine logs, so you can always audit what it did.
Propose-then-apply writes. Any change Archer wants to make to your application is returned as a proposal. You review the diff and click Apply when you are ready. Read tools run freely, write tools always go through your approval. See Mind Sessions.
Persistent memory. Archer remembers. Every fact, every evidence span, every interview answer, every dean brief version, every essay revision is stored and re-used across sessions. You never have to re-explain yourself, and the engine only gets sharper as you add material.
How it fits in the engine
This page is the fits-in-the-engine page. Every other doc in this guide describes one stage or one surface of the orchestration loop. When you are ever confused about where a feature sits, come back here and find the stage it belongs to: Ingest, Interrogate, Synthesize, Draft, Orchestrate, or Submit.