Prototype Profile

Purpose

Use for a time-bounded artifact whose main output is learning about a stated hypothesis. It MUST be reassessed before production use or compatibility promises.

Priority and defaults

Delivery speed and correctness of the experiment precede simplicity, maintainability, and performance.

Core Skill	Mode	Rationale
code-clarity	minimal	Keep the experiment understandable without polish.
abstraction-and-reuse	conservative	Avoid hypothetical production abstractions.
modular-design	feature-oriented	Keep the experiment in one bounded slice.
contracts-and-errors	strict-boundaries	Preserve valid evidence and safe authority.
dependencies-and-boundaries	framework-native	Use direct conventional mechanisms.
performance-and-resources	clarity-first	Measure only what the hypothesis requires.
testing-strategy	unit-focused	Verify decisive logic cheaply.
safe-change	redesign-authorized	Favor reversible learning over compatibility.

Policy

State the hypothesis, success signal, time box, real-world risks, and disposal or promotion decision. Shortcuts MAY reduce production hardening but MUST NOT expose real secrets, users, irreversible data, or excessive authority. Unstable interfaces MUST be labeled as such.

This profile has no automatic modifier. Production, public, or security constraints activate their normal modifiers and may make a prototype approach inappropriate.