The canon turns taste into constraints a team can reuse.
CREATE SOMETHING .ltd
A canon for decisions that earn their place.
CREATE SOMETHING .ltd turns philosophy, standards, voice, and patterns into practical judgment for building less, but better.
Principles, standards, and language for work that has to hold up.
Decisions should leave behind language, standards, and examples.
Principles connect back into research, runtime practice, and delivery.
Canon
principles that guide judgment
Masters
reference points for quality
Standards
operating rules for the work
Voice
language that keeps decisions clear
Operating canon
Weniger, aber besser.
Less, but better is the rule for how CREATE SOMETHING evaluates research, design experiments, and delivery work. The canon exists so that judgment can travel.
Not minimalism for its own sake. When you remove the unnecessary, what remains gets stronger.
- Every feature, word, and decision has to earn its place
- Simple takes more effort than leaving the work complicated
- The canon makes that effort repeatable
Before adding another surface, pattern, or claim, the property asks whether it helps the next decision.
- Reduce until the operating intent is legible
- Keep the useful constraint and remove the ornamental one
- Make judgment visible enough for another team to reuse
The standard only matters if it moves into research, runtime practice, and scoped delivery.
- Research uses the canon to decide what evidence matters
- The workbench tests whether the principle survives runtime
- Delivery turns the decision into a controlled workflow
Featured pattern
Crystallization turns judgment into an operating artifact.
The strongest ideas in the canon are not decorative. They become constraints, quality gates, routing decisions, and review paths.
Crystallization Policy before prompt
Encode human expertise into configurable constraints that AI agents execute within.
- Model routing, quality gates, and review pipelines become policy
- Human judgment shapes every decision without requiring constant presence
- The artifact is specific enough to run and clear enough to review
The useful output is a reusable operating document, not another one-off instruction.
- Constraints should be versioned, inspectable, and explainable
- Prompt language follows the policy instead of replacing it
- Reviewers can see what judgment was encoded
Featured masters
Reference points for quality.
The masters are not there for nostalgia. They give the work a higher bar for restraint, legibility, and usefulness.
Creation moat
MCP consumption is commoditized. MCP creation is not.
The canon names the standard, the research documents the evidence, the workbench tests the runtime, and the agency turns the fit into governed workflow delivery.
Research with receipts
Reference implementations and operating notes that make a claim defensible before it becomes delivery.
Runtime practiceIntegration experiments and pattern validation before the idea becomes a documented operating rule.
Governed workflow deliveryCustom MCP and automation work shaped by policy, controls, owners, and handoff evidence.
Property progression
Turn the canon into the next operating decision.
Start with the principles, read the research when the claim needs evidence, use the workbench when it needs runtime proof, and book a mapping session when it belongs in the business.
You are here .ltd Canon
- 01 .ltd Canon Clarify the principles, standards, and judgment that should guide the work.
- 02 .io Research Read the evidence, patterns, and operating notes that make the claim defensible.
- 03 .space Workbench Try the routes, tools, and runtime behavior before the pattern becomes delivery.
- 04 .agency Build Turn the fit into a scoped workflow with controls, owners, and handoff notes.