Assigning Aniimo jobs in Homeland
Homeland output depends on assignment quality, not headcount. Match available Aniimo to the resource bottleneck, then review whether each task still supports the next expedition.

Start from the bottleneck
Read your job board backwards: identify the material that blocks your current team, capture or upgrade plan, and staff that production first. Idle balance across all tasks is slower than focused coverage.
- One named bottleneck per review cycle.
- Staff the bottleneck fully before spreading workers evenly.
- Leave decorative tasks unstaffed until production is stable.
Match Aniimo to work honestly
Assign only work the current client confirms an Aniimo can perform, and prefer clear aptitude over sentiment. A mismatched worker is a hidden vacancy.
- Check task eligibility in the client rather than assuming by theme.
- Rotate expedition regulars out of long tasks before you need them.
- Note which assignments produce visibly faster—beta values are unpublished.
Review on a fixed rhythm
Once per session, collect output, compare it to the plan, and reassign. The board drifts silently as unlocks arrive; a weekly-feeling review catches idle workers and finished bottlenecks.
- Collect and restart loops at session start, when attention is cheap.
- Replace any assignment that produced nothing you used.
- After each patch, re-verify task lists before trusting old routines.
Field note template
Keep observations reproducible
Write down your region, test build, Aniimo form, level, teammates, target and result. A useful beta note explains its conditions.
