Why
I build around incentives, agency, and repair: tools and systems people can inspect, fork, maintain, and adapt without asking permission.
Posture
I am not neutral about authority, dependency, or permission.
I do not treat institutional approval as legitimacy. I do not treat compliance as morality. I do not assume the state, the market, or the boss is owed the first claim on what people are allowed to build.
The work exists because dependency is treated as normal, institutions mistake control for order, and people are trained to wait for approval from systems that profit from their hesitation.
The problem
Most modern systems ask people to trust things they cannot inspect, obey rules they did not consent to, rent tools they cannot repair, depend on institutions they cannot meaningfully exit, and accept incentives that reward extraction over stewardship.
This is not only a political problem. It is a design problem.
A system can be efficient at extracting value while making everyone inside it less capable. I care whether a system preserves agency, repair, local knowledge, public records, forkable tools, and the ability to act before permission arrives.
Incentives
Incentives are architecture.
Money, debt, rent, credentials, employment, law, platform access, and institutional permission shape what people are rewarded for doing. Bad incentives reward extraction, silence, waste, gatekeeping, and obedience. Good incentives reward stewardship, repair, honesty, skill, care, and durable public value.
The useful question is direct: what does this system reward, and who becomes more capable by using it?
Agency
Agency is usable knowledge plus real options.
A person has more agency when they can read the rule, inspect the code, hold the key, repair the tool, understand the cost, leave the arrangement, fork the pattern, or teach the next person how it works.
Permissionless systems are not about isolation. They lower the cost of honest participation.
Repair
Repair means systems should remain understandable after launch. Tools should be maintainable. Records should be checkable. Claims should be labeled. Failure notes should survive.
Documentation is part of repair. It turns private work into something another person can verify, reuse, criticize, adapt, or reject.
Project map
| area | why it belongs here |
|---|---|
| Onchain demos | Public rules: custody, randomness, lifecycle, operator power, and user safety. |
| Market research | Incentive surfaces: price, behavior, signal, noise, and the limits of models. |
| Procedural tools | Clear labels for what is observed, modeled, inferred, or aesthetic. |
| Rust CLI tools | Low-noise utility: compact, inspectable output for humans and tools. |
| Heterarchy | Long-horizon structure: distributed authority, cooperative organization, and adaptive capacity. |
Civilizational cost
When working knowledge systems are destroyed, the replacement is not automatically better. Sometimes the replacement is only easier to control, insure, bill, or standardize.
Fire is the clean example. Cultural burning maintained healthier landscapes for generations. When that practice was criminalized and replaced by centralized suppression, fuel loads and ecological fragility compounded. The later cost shows up as catastrophic fires, emergency budgets, insurance failure, smoke, dead forests, and cancer exposure for the people sent into the failure.
Adaptive capacity is the real bottom line: skill, trust, repair, local knowledge, ecological health, public records, forkable tools, and communities able to act before permission arrives.