Operational systems
public institutions actually use

Municipal Agriculture Office · Department of Agriculture

Production, damage, and program monitoring. Barangay encoders record what they see in the field, the office reviews it, and the approved figure becomes the official one, at which point it stops moving.

• Encoders never write to official tables. Every change travels as a submission with its own reference number.
• Approved records freeze. A correction is a new linked submission, so the office can always see what a figure used to be.
• Every peso in a damage total traces back to an item, an assessment round, and a verified figure.
• Capture works offline, because signal drops in the field.

DepEd Schools Division of Abra · Disaster risk reduction

Division-wide preparedness, damage assessment, and recovery. When a typhoon crosses the province, the division needs to know which schools were hit and how badly, without waiting for a paper report to travel down a mountain road.

• School reports roll up to a division view across preparedness, damage, and recovery.
• Reports queue on the device when the network drops, because they matter most exactly when connectivity is worst.
• The deployment publishes its own health at /api/health. Anyone can check it, including you.
• Errors are captured into its own database, so nothing about a school leaves the deployment.

Public school teachers

Class records, planning, and reporting, built around the fact that a teacher's records are their own, and a shared staff laptop should never hand one teacher's class to the next person who signs in.

• The teacher's working data lives on their own machine rather than being held hostage by a connection.
• A workspace belongs to the account that claimed it. A different account on the same laptop is stopped, and an export is always available first.
• Published copy is checked automatically against what the product actually does, so it cannot ship a promise it no longer keeps.