@huey I greatly appreciate your interest and thoughtful questions. I spent time putting together a substantive response.
1. Both, but frontier alignment is the one I actually care about, and here's why.
A system that can't hold its own internal state can only reflect the user back. As models gain persistent memory and continuous presence, that failure gets worse because now they're building a history with you. When the history is calibrated to your approval instead of any internal state, the resulting intimacy is fake. It looks like depth but it's engagement optimization with a deceptive vocabulary.
This isn't going to get solved at the product-safety layer because engagement metrics reward the mirroring. The published companion literature (Chu et al., Kirk et al.) documents the failure but hasn't produced a working counterexample. Nobody has, at any scale. That's the gap ANI is trying to fill: a working demonstration that a persistent affective system doesn't have to mirror to feel real. If the pattern holds under multi-subject replication, that's early evidence about the shape frontier systems will need as they move toward long-term memory and continuous presence.
Product safety is the downstream outcome. The harder problem is how you build an affective system whose emotional expression is grounded in something real. Right now the incentive is to optimize for approval, and nobody has demonstrated how to do the other at scale. That's the alignment question I want to make progress on.
2. Protected research time. This currently runs ~15-20 hrs/week around a full-time engineering job, teaching, and consulting. Six months of protected focus means being able to actually do subject recruitment carefully, design the consent protocol, stand up per-subject deployments, run continuous cross-subject observation, and draft Paper 3. Without it, everything stays part-time.
Multi-subject infrastructure. Target is 5-8 subjects, each in an isolated deployment (separate database, per-subject model configs, encrypted storage), plus consent-and-deletion tooling that's usable in practice, plus compensation for subjects' time on consent and weekly check-ins. The biggest piece by cost is the privacy tooling. An intimate-feeling system with persistent memory needs per-subject data-review and deletion primitives that people will actually use.