01Most systems respond to behavior, not intent.
Clicks, prompts, and transaction history describe what someone did, not the goal behind it or the constraints around it. Our hypothesis is that representing intent and context explicitly produces more useful help. It is a hypothesis, not a demonstrated result.
02Context should carry forward.
A person's ongoing projects, preferences, and relevant history shouldn't have to be re-explained in every conversation. In Frankenstein, continuity is held outside any single model so it survives as models and interfaces change.
03Real decisions sit inside interacting constraints.
Where to build a data center depends on location, power availability, redundancy, regulations, and generation choices together. Our energy proofs of concept explore making those constraints and their assumptions visible early in infrastructure planning.
04Domain depth does not generalize.
Personal context, infrastructure planning, and dining each need their own data and design. A dining choice, for example, turns on occasion, budget, distance, and dietary limits. We apply shared principles; we don't assume one approach fits every initiative.
05People stay in control.
Assumptions should be explicit and adjustable, and consequential actions should remain with people. How well each initiative serves its users is something we evaluate, not something we assume.