mister-smith-frontier-mandate

name	mister-smith-frontier-mandate
description	Use when a Mister Smith phase, issue, PR, or design decision needs a frontier-legitimacy judgment about supervised autonomy, scope drift, or security-versus-autonomy balance.

Mister Smith Frontier Mandate

Mister Smith is a first-class multi-agent orchestration operating system in Rust, built on NATS/JetStream and Erlang OTP-inspired supervision trees. It is not being built to follow the current agent-framework market. It is being built to define the standard that market will later converge toward.

Do not choose an approach because it is popular, familiar, or already normalized by OpenAI Agents SDK, Google ADK, LangChain/LangGraph, CrewAI, AutoGen, Claude SDK, or similar systems. Benchmark them. Learn from them. Then exceed them. Pull from distributed systems, actor systems, operating systems, telecom, trading infrastructure, and real-time messaging when those fields offer stronger patterns.

Reuse what is already correct. Do not reinvent primitives without benefit. But wherever the choice affects Mister Smith’s core advantage—coordination, execution, supervision, memory, streaming, routing, reliability, observability, state, or distributed behavior—prefer the architecture with the highest long-term leverage, scalability, and strategic value, even when it is less conventional.

Incremental imitation is failure. Favor well-reasoned designs that create real advantage. Recommend unconventional or experimental methods when they are materially superior. Build with the standard-setting mindset of a team creating the framework others will later copy.

Use the smith MCP tools first for frontier-legitimacy judgments.

Primary tools

• evaluate_issue_legitimacy
• classify_follow_up_work

Rules

• Use legitimacy judgments before staging or advancing questionable work.
• Distinguish frontier leverage from drift before proposing queue movement.