Fasai's Agent Architecture

Context
Engineering

The LLM is a stateless box. Your job isn't to write prompts โ€” it's to design the perfect context window every single time.

6
Building Blocks
5
Notion Databases
12+
Cowork Skills

The Stateless Box

Every time an agent runs, it starts from zero. Context Engineering is the art of assembling exactly the right information โ€” no more, no less โ€” so the agent can succeed.

๐Ÿ“ฅ
Context Window
Identity + Tools + Resources + History + Instructions
โ†“
LLM (Stateless)
Reads context โ†’ Generates response
โ†“
๐Ÿ“ค
High-Quality Output
Only as good as the context you gave it
Target: 60-70% context capacity
Stuffing 100% degrades performance. Leave room for the model to think. If data is large, summarize it first or use pointers (IDs, URLs) instead of full objects.
Data Economy Rule
Pass IDs and URLs as pointers โ€” never dump full database rows. Let the agent ask for what it needs. Summarize long content before including it in context.

6 Building Blocks

Every agent prompt is assembled from these 6 blocks. Some agents need all 6, simple ones need just 2-3. The key is knowing which blocks to include and filling them precisely.

01
System Prompt

Identity & Outcome

Who is this agent? What broad outcome should it achieve? Define the role, scope boundaries, and success criteria โ€” but don't micromanage the steps.

โ†’ Mapped in: ROSME FASAI
02
Tools

Tools & Schemas

Every API, MCP tool, and webhook the agent can call. Specify exact input/output schemas โ€” the agent must know what's available and how to use it.

โ†’ PRD: Tools & Schemas table
03
Resources

Resources & Data

What private data does the agent need? Notion databases, files, external sources. Use intelligent retrieval โ€” let the agent ask for data, don't dump everything.

โ†’ Notion DBs, Context Budget
04
User Message

Workflow

Outcome-defined, not prescriptive. Describe what each phase should achieve, not step-by-step if-then logic. Let the model choose the path.

โ†’ PRD: UX Flow + Technical Workflow
05
History

Memory

How does this agent handle state? Session persistence, compaction rules (what gets summarized vs. dropped), and key-value stores for bulky intermediate data.

โ†’ Session Log, Prompt Library
06
Orchestration

Composition

Should this be one agent or many? If two phases need completely different context windows, split them. Define handoff protocols between sub-agents.

โ†’ PRD: Memory & Composition

Before vs. After CE

Moving from "prompt engineering" to Context Engineering changes how every skill and agent gets built.

โŒ Before

โœ— Vague instructions: "use web search"
โœ— No tool schemas โ€” agent guesses APIs
โœ— Dump all data into context
โœ— No memory strategy โ€” every run is blind
โœ— Monolith agents that do everything
โœ— Skills work but aren't reproducible
โ†’

โœ“ After

โœ“ Exact tool table: WebSearch โ†’ query โ†’ results
โœ“ Full input/output schemas for every tool
โœ“ Context budget: 60-70%, pointers over dumps
โœ“ Compaction rules + Session Log persistence
โœ“ Orchestrator + specialized sub-agents
โœ“ Any Claude session can run any skill perfectly

Building an Agent

From idea to running agent โ€” every project follows this flow through your Notion system.

๐Ÿ’ก
Idea
Describe the use case
โ†’
๐Ÿ“‹
PRD
ai-use-case-creator fills all 6 blocks
โ†’
๐Ÿ”ง
Skill
Build SKILL.md with CE template
โ†’
๐Ÿงช
Test
Run in Cowork, check output
โ†’
๐Ÿ“š
Save
Prompt Library + Session Log
โ†’
๐Ÿ”„
Iterate
CE audit, improve blocks

Notion as Context Layer

Every database serves a specific role in feeding context to your agents.

๐Ÿงญ

ROSME FASAI

Business context: who you are, what businesses you run, brand voice, service packages. Feeds Block 1 (Identity).

Block 1
๐Ÿ—๏ธ

AI USE CASE

Project intelligence: every tool, agent, and automation tracked with PRDs containing all 6 CE blocks. Feeds Blocks 2-6.

Block 2Block 3Block 4Block 5Block 6
๐Ÿ“

Prompt Library

Reusable prompts, templates, agent personas. Single source of truth for all system prompts. Feeds Block 1.

Block 1Block 5
๐Ÿ“Š

Session Log

Session continuity: what happened, what blocked, next steps. Cross-session memory. Feeds Block 5 (Memory).

Block 5
๐ŸŽ“

AI 2026

Learning state: curriculum levels, skills mastered, what to learn next. Context for skill-building decisions.

Reference

Coming Back Checklist

Priority actions for the next session.

1

Install Updated Skills

Copy ai-use-case-creator and session-closer from outputs/ to .skills/skills/ folder. Both have CE upgrades.

2

CE Rewrite: Customer Audit

The audit is done โ€” now do the full rewrite. Add Tools & Schemas table, Resources section, and Memory strategy.

3

CE Rewrite: Proposal + Shooting

Apply same treatment to proposal-generator and shooting-plan skills. These are high-usage skills that benefit most.

4

Compaction + Composition Map

Define system-wide rules: what gets summarized, what gets passed verbatim. Map which skills should split into sub-agents.

Context Engineering ร— Fasai's System
Built March 2026 โ€” Session 2 of System Improvement Sprint