Maida
The first concrete tool: a game-launching space for the pause before play. Maida should be framed as a threshold tool, not as a recommendation engine.
Project Atlas
The home page starts with a recognizable moment. This atlas keeps the public routes clear after someone wants the map.
The first concrete tool: a game-launching space for the pause before play. Maida should be framed as a threshold tool, not as a recommendation engine.
The explanation layer. Akatsuki names the experiences behind Bright Raven: choice overload, agency, friction, anti-recommendation, and human-AI judgment.
The incubator for unfinished but alive instruments. Lab makes experiments visible without pretending they are finished products.
The umbrella domain. Its job is not to list everything first, but to help people recognize the experience that makes the projects matter.
A map of thinking paradigms for the moment when a problem needs a better lens before it needs a faster answer.
A startup research engine for daily signal gathering, idea filtering, and founder-facing research loops.
A reading and decision map for turning research into judgment, especially around predictive processing and human-AI decision making.
Long-term universe direction for games, narrative systems, and agency research. It is a north star, not the immediate validation target.
A concept around naming, reflecting, and letting go of emotional states. It belongs in the atlas as a direction, not as a launched public product.
An integration direction around command-line, API, and game interfaces. The boundary is still intentionally unresolved.
Infrastructure direction for a future API surface. It should be listed as planned infrastructure until a public contract exists.
Some client work, household tools, external-role work, internal research, and archived experiments are intentionally not promoted as Bright Raven public products. The atlas should make public orientation easier without exposing work that needs a narrower context.