# Baucon project instructions

Apply this block to the project’s own instructions (for example, append it to AGENTS.md). Pin the Baucon kit version and record which medium and behavior contracts you adopt.

## Design with Baucon

Read the current Baucon Design Baseline in the canonical Obsidian specification before designing. For portable projects, use DESIGN-BASELINE.md from kit 0.1.4 or later. Apply the current type, component, and motion defaults where relevant. Use gallery-specific numeric values as reference parameters.

Use Baucon as a design system for this project. Begin with the material and the task: identify where the work is read, what the user needs to know or do, and which constraints should give the expression its character. Treat Baucon First Principles v1, Panda UI and Operational Doctrine, and Operational Controls and Motion v1 as authoritative. Treat gallery colors, type, depth, and other values marked “Gallery proposal” as starting points for this project. Treat SOFO measurements as reference values unless an accepted contract says otherwise.

Use geometry to organize, identify state, or guide attention. Give spatial layers explicit roles: context, evidence, and active selection. Keep reading and focus order meaningful when the composition is flattened, and do not encode confidence or data height solely through visual elevation. Choose clear labels and a flat alternative where the depth carries information.

Separate event time from interface motion. State what is observed, inferred, modeled, delayed, or unavailable. Use one purposeful gesture at a time to show a cause, continuity, or change in state. Keep hit areas stationary, respond to repeated input, and preserve the outcome without motion. Preserve native controls and semantics, visible focus on non-text controls, caret-only focus on text and search fields, accessible names, keyboard operation, and usable touch targets. Use 44 px primary and icon targets for the operational profile. Make hover optional.

Start Panda UI with alignment, legibility, and predictable operation. Keep the context canvas fixed; put labels near their source and use joined surfaces with one seam. Provide compact controls, a contextual workspace, and a separate place for evidence and limits. Keep square frames as the paper default. Use paper and ink for map selection, use the borderless pulsing green dot for LIVE and saturated green for Reset feedback, and explain feed health separately. Keep scrollbars quiet and preserve native scrolling.

When an image calls for a print impression, use the existing Xerox Plate skill. Use flat ink on the actual receiving surface, with transparent negative space and no feathering or continuous gray wash. Keep text and controls above the plate. Treat the portfolio paper palette and hatch geometry as one documented material expression.

Map local semantic tokens to the adopted Baucon values before creating new ones. Record overrides with their reason and scope. Test narrow layouts, long labels, touch and keyboard input, reduced motion, and state interruption. Record evidence and limitations. Keep project exceptions local; propose changes to the shared system separately. Never claim adoption in another project or edit a reference implementation without a separate request.

For each reusable component or behavior, include an interactive specimen, provenance, token values, state and timing rules, reduced-motion behavior, acceptance criteria, and runnable implementation code.