Reusable patterns
Room, rack, stack, enclosure, incubator, and setup templates.
Beta 81 user guide
Housing Templates & Setup Acceleration
Create reusable, governed Housing patterns and apply them to dozens or hundreds of positions without repeating every Blueprint, equipment, environmental, and maintenance field.
Species Intelligence remains advisory. Suggested starting values are visibly identified, require explicit review, and never silently overwrite fields marked verified.
Permanent versions
Every saved change receives an immutable version and change note.
Governed approval
Managers author; owners and administrators approve organization use.
Full review
Nothing is created until the user reviews differences and confirms application.
Create and apply a Housing template
1
Create or clone a template
Open Housing Templates. Start with a blank room, rack, stack, enclosure, incubator, or setup template, or clone an existing Housing record. Cloning copies recorded structure into a draft; it never changes the source Housing.
2
Review the physical structure
Confirm the Housing record type, physical profile, capacity, generated child patterns, names, codes, and Housing Blueprint geometry. Use {n} or {nn} in repeated child names and codes.
3
Add the operational setup
Add standard equipment bundles, environmental-zone starting values, recurring maintenance routines, intended species, safety notes, and general setup notes.
4
Protect verified settings
Mark any section that must not be replaced by Species Intelligence suggestions or a later template update. Protected differences remain visible in the review and require a separate decision.
5
Save an immutable version
Enter a change note and save. PMA creates a new permanent version and returns an updated approved family to draft until it is reviewed again.
6
Approve the current version
An owner or administrator approves the current version. Managers can create and revise templates, but approval is deliberately separated from authorship.
7
Preview the application
Choose the destination, quantity, naming prefix, code prefix, and starting number. Review every planned Housing record, equipment record, environmental zone, maintenance routine, warning, conflict, and protected difference.
8
Confirm bulk creation
Only an approved current version can be applied. PMA writes the reviewed records and records permanent application evidence. It does not silently update animals or assign animals to the new Housing.
Template states
Draft: editable through new immutable versions, but unavailable for application.
Approved: the current version can be applied after a full review.
Superseded: retained for evidence after a replacement family or governance decision.
Archived: hidden from active use while version and application history remains intact.
Difference preview
Will be added: new Housing, equipment, zones, or routines.
Will be changed: an explicitly reviewed difference on an existing target setup.
Unchanged: current and proposed values already match.
Protected: a verified setting will remain unchanged.
Conflict: the application cannot proceed until the conflict is resolved.
Important boundaries
- • A template does not certify that a Housing setup is suitable, safe, code-compliant, or appropriate for a specific animal.
- • Species Intelligence starting values are not verified user settings and do not replace professional husbandry judgment.
- • Applying a template does not move animals, assign animals, clear quarantine, override BioShield restrictions, or complete maintenance work.
- • Template application can create many records. Review the exact count and naming plan before confirmation.
- • Rolling back the Beta 81 template schema does not delete Housing already created by an applied template.
Troubleshooting
The template cannot be applied
Confirm the current version is approved. Editing an approved template creates a new draft version that must be approved again.
A Species Intelligence suggestion did not change a field
That field may be marked verified. Remove protection only after reviewing the verified value and deliberately deciding to replace it.
The planned count is much larger than expected
Review both Systems to create and every generated child quantity. The preview counts parent and child Housing records.
The template tables are missing
Complete the Beta 81 database migration after both the Quality Gate and Vercel Preview pass. Before migration, PMA shows an empty template library instead of failing the rest of Housing.
An application partially fails
Do not rerun blindly. Review the database error and application evidence. The RPC validates organization scope and reviewed record structure before creation.
Expected result
After confirmation, PMA creates the exact reviewed Housing structure and selected setup records, records which approved template version was used, preserves protected settings, and leaves animals and unrelated operational records unchanged.