Published Research Β· My Contribution to AI

The ROSTR Framework

A unified architecture for production-grade multi-agent systems with phase-aware orchestration and persistent knowledge compounding. Four components. A five-phase taxonomy. Running in production today.

Why ROSTR exists

Multi-agent AI systems suffer from four fundamental problems: context loss between sessions (agents restart from scratch), naive routing (keyword matching instead of phase-aware allocation), brittle retrieval (single-pass search without credibility control), and raw prompting (no compilation, no parameterization, no reproducibility).

ROSTR solves all four. It formalizes agent invocation into a compiled manifest (PAL), retrieves knowledge with stratified credibility (RAG DAL), classifies and allocates work with a 5D phase taxonomy and 4D priority score (NPAO), and persists state across sessions with scoped namespaces (Rostr Hub).

The framework was published in April 2026 through Zenodo with DOI 10.5281/zenodo.19550414. It is the engine behind the Gency AI agency β€” turning SOPs into intelligent agents β€” and a contribution to the multi-agent systems field.

The four components

01
PAL β€” Prompt Abstraction Layer
The Intent Compiler

PAL transforms loose natural language into strict agent runtime manifests. Instead of sending raw prompts to models, every agent invocation flows through a five-stage compilation pipeline:

  • Stage 1 β€” Intent Extraction: Parses primary intent, domain, subject, constraints, desired output, urgency, and ambiguity score from the user's natural language.
  • Stage 2 β€” Context Injection: Loads session state, project context, org context, and team conventions from the Rostr Hub. Budget-managed: max 8000 tokens with priority ordering.
  • Stage 3 β€” Semantic Enhancement: Expands ambiguous verbs, adds missing precision, decomposes compound goals into phase sequences, removes hedging language, injects domain best practices.
  • Stage 4 β€” Runtime Compilation: Produces a structured YAML manifest: agent type, model, temperature, max parallel tasks, timeout, behavior profile, tool permissions, memory mode, output format, verification method.
  • Stage 5 β€” Output Routing: Routes the compiled manifest to the appropriate execution layer based on domain and phase.
# PAL Runtime Manifest (compiled) runtime: agent_type: builder model: claude-sonnet-4 temperature: 0.2 instructions: behavior_profile: analytical completion_criteria: [tests pass, review approved] tools_enabled: allow: [file_system:read, code_execution] deny: [file_system:write:production]
02
RAG DAL β€” Dynamic Acquisition Layer
Autonomous multi-pass retrieval with source credibility stratification

RAG DAL replaces naive single-pass search with a three-tier credibility architecture:

  • Tier 1 β€” Primary & Authoritative (credibility 1.0): Academic papers (arXiv, PubMed), official docs (.gov, standards bodies), university repositories. Used to establish ground truth.
  • Tier 2 β€” Verified & Editorial (credibility 0.75): Major news outlets, trade publications, analyst reports (Gartner, McKinsey). Used to contextualize Tier 1 findings.
  • Tier 3 β€” Community & UGC (credibility 0.40): Blogs, social media, forums, Stack Overflow, Reddit. Used for real-world signal, sentiment, and edge cases.

The retrieval algorithm runs multi-pass: broad sweep β†’ gap fill β†’ deep verification. Each pass assesses coverage per sub-topic using a confidence scoring formula that weights source count (35%), consistency (30%), tier distribution (25%), and recency (10%). Pass 4 only triggers if two or more topics remain below the 0.6 threshold β€” at which point they're marked unresolvable.

03
NPAO β€” Navigate, Prioritize, Allocate, Orchestrate
Phase-aware task routing with 4D priority scoring

NPAO is the operational brain. It classifies every task into one of five phases, scores it on four dimensions, and allocates it to the optimal agent.

5D Phase Taxonomy:

P0
PreD
"Is this worth building?"
Problem definition, competitive research, feasibility, go/no-go. NO code written.
P1
Design
"What are we building?"
Architecture, UI/UX, data models, API contracts, tech stack decisions.
P2
Development
"Does it work?"
Implementation, testing, code review, documentation. Builder agents dominant.
P3
Deployment
"Is it safe to ship?"
CI/CD, staging QA, canary deploys, monitoring, rollback procedures.
P4
Debugging
"What broke and why?"
Root cause analysis, fix, regression testing, post-mortem. Investigate-first.

4D Priority Scoring: Phase Urgency (0-10) Γ— 0.35 + Dependency Impact (0-10) Γ— 0.30 + Business Impact (0-10) Γ— 0.25 + Resource Efficiency (0-10) Γ— 0.10. Tasks scoring β‰₯7.0 get immediate allocation; 4.0-6.9 are queued; below 4.0 goes to backlog.

Agent Allocation: Eligible agents are filtered by phase compatibility, tool availability, and dependency status. Each is scored on context similarity (50%), specialization overlap (35%), and current load (15%). Highest scorer wins.

Orchestration patterns: Sequential chain (A→B→C), parallel fan-out (A→[B,C,D]), aggregation fan-in ([A,B,C]→E), conditional branch (A→decision→B or C).

04
Rostr Hub β€” Agent Operating System
Persistent reference architecture with four-level state management

The Hub is what makes knowledge compound across sessions instead of evaporating. Four levels of state:

  • Level 1 β€” Session State (ephemeral): Active tasks, in-progress work. In-memory / Redis cache.
  • Level 2 β€” Project State (persistent): Decisions, artifacts, learnings, history. File-based + vector DB. This is where the compounding happens.
  • Level 3 β€” Organization State (evolving): Identity, ICP, positioning, team structure. Version-controlled file store.
  • Level 4 β€” Agent State (portable): Skills, preferences, calibration, performance stats. Agent-specific namespace.

Cross-namespace access requires permission. Knowledge retrieval uses hierarchical credibility β€” not all sources are equal. Every project gets a directory under rostr-hub/projects/{id}/ with knowledge-base, learnings.jsonl, timeline.jsonl, and checkpoints.

Everything ROSTR

Where ROSTR runs today

🏒
Gency AI β€” Project Intake System

The ROSTR framework powers the project intake system at Gency AI. When a client submits a raw SOP or idea β€” notes, files, links, a one-line description β€” PAL compiles the intent, NPAO classifies the work phase and scores priority, and the system outputs a complete project package: knowledge base, PRD, architecture diagram, reporting framework, and phased build plan. Idea β†’ fully-scoped agent: hours β†’ under 30 minutes.

πŸ€–
Gency AI β€” Agent Development Agency

The agency's core product pipeline runs on ROSTR: JTBD Analysis captures the operator's functional requirements β†’ PAL/NLP extracts and compiles the intent β†’ the ROSTR System delivers the agent, workflow, or skill. Every client engagement from SOP to deployed agent follows this path.

πŸ›οΈ
Your48 β€” Civic Intelligence Platform

The data sync pipeline that ingests 1,500+ business licenses from Chicago Data Portal daily uses ROSTR's NPAO task router for phase classification and cron orchestration. $0/month infrastructure on Vercel free tier.