[ Case studies ]
Work that can be inspected.
These are selected public examples of work operated by Maha Strategies. Each account links to the live work, says what is actually available, and states the boundary we do not want visitors to mistake for a promise.
[ A note on evidence ]
These are not performance claims, client testimonials, or a substitute for independent review. They are operating notes: public artifacts, their intended use, and their limits.
[ Public-interest education ]
Mayon: a free educational volcano experience
Maha Strategies built and maintains a free, true-scale Mayon Volcano experience for learners, educators, and curious visitors. It pairs terrain, historical chapters, explanatory interior diagrams, and bounded hazard scenarios with a teacher kit and published methods.
What is live
- — A public interactive, classroom materials, and an explorable historical and hazard-learning experience.
- — A methods and data page describing terrain, imagery, inferred-interior limits, scenario assumptions, update policy, and official-source boundaries.
Operating boundary
It is not a live warning, monitoring, forecast, evacuation, or location-specific decision system. Interior features and hazard corridors are explanatory inferences and teaching overlays. Current conditions and instructions belong to PHIVOLCS and local authorities.
[ Accountable-release infrastructure ]
Agentic Publishing: making a release inspectable
Maha Strategies operates an experimental publishing environment that treats a published work as a versioned, reviewable object rather than a static file alone. The public materials make the proposed architecture, source boundaries, and release artifacts inspectable.
What is live
- — A public technical architecture guide and a read-only Context Pack Explorer with a release manifest, source ledger, exclusions, and machine-readable JSON.
- — A release model designed around human approval, auditability, and deliberately bounded public metadata rather than automatic publication by a model.
Operating boundary
The public explorer is a demonstration of the release contract, not a claim that every source text is public or that an AI system can guarantee truth. The longer-term architecture remains a roadmap where it is not yet implemented.
[ Privacy-conscious tools ]
Apps: useful defaults, documented boundaries
Maha Strategies publishes public documentation for Mayon, Maha OS, and The Dream Engine. The products are designed around understandable scope, user agency, and public privacy information rather than opaque data collection as a default.
What is live
- — Maha OS is available on iOS and Android; The Dream Engine is available on Google Play; Mayon is live on the web with mobile releases in preparation.
- — Each product has a public description, support route, and privacy documentation or stated data boundary that visitors can inspect before they use it.
Operating boundary
Privacy-conscious does not mean that no data can ever leave a device. Product-specific documentation explains the relevant limits, and user-initiated features or third-party platforms have their own terms and practices.
The operating entity
Maha Strategies is the operator and publisher connecting these public projects. Their evidence, data practices, audiences, and claims remain distinct. The Maha Knowledge Network maps the relevant relationships; the underlying sites remain the primary source for each project.