@createsomething/pi-three-tier-framework

The Three-Tier Framework (Database, Automation, Judgment) for agent systems — as a Pi coding agent package. Classify components, debug systems, and design MCP servers using the structural model behind CREATE SOMETHING.

Packages

Package details

skillprompt

Install @createsomething/pi-three-tier-framework from npm and Pi will load the resources declared by the package manifest.

npm repohome report
$ pi install npm:@createsomething/pi-three-tier-framework
Package
@createsomething/pi-three-tier-framework
Version
1.0.5
Published
Aug 24, 2026
Downloads
1,209/mo · 17/wk
Author
micah-createsomething
License
MIT
Types
skill, prompt
Size
17.5 KB
Dependencies
0 dependencies · 0 peers
Pi manifest JSON
{
  "skills": [
    "./skills"
  ],
  "prompts": [
    "./prompts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

@createsomething/pi-three-tier-framework

The Three-Tier Framework (Database, Automation, Judgment) for agent systems — delivered as a Pi coding agent package.

Install

pi install npm:@createsomething/pi-three-tier-framework

Source price: $0 under the MIT License. Managed CREATE SOMETHING Control is a separate service, available from $900/month.

What You Get

Skills

  • /skill:three-tier-framework — Load the full framework reference, tier definitions, debugging heuristic, and MCP mapping
  • /skill:deep-module-design — Design modules for leverage, locality, testability, and clear tier ownership

Prompt Templates

  • /classify — Classify any system component into framework tiers
  • /debug-tier — Apply the three-tier causality heuristic to debug a failure
  • /mcp-design — Design an MCP server using the framework

The Framework

Every agent system has three tiers, mapped to MCP's three primitives:

Tier What MCP Primitive Control Model
Database What exists (state, records) Resources Application-controlled
Automation What happens (tools, skills) Tools Model-controlled
Judgment What should happen (policy) Prompts User-controlled

Debug order: Always check tiers in sequence — Database → Automation → Judgment. Lower-tier failures cascade upward.

The recursive property: MCP's sampling mechanism allows Automation to request Judgment, creating a feedback loop that mirrors embodied cognition.

Policy as artifact: Constraints flow through all tiers as data — stored in Database, transformed by Automation, evaluated by Judgment.

Learn More