An open record · A growing platform
Development journey
GraceWays began with a question: how can knowledge about an animal stay together when messages, people and devices change? Each development step answers a practical part of that question.
01 · Concept work · July 2026
An open animal record
- What already existed?
- Experience with rescue organizations and the need to preserve an animal’s story, care information and media.
- What problem emerged?
- Information was scattered across messages, notes and devices. Records needed to remain readable independently of a particular application.
- How did GraceWays develop?
- An animal-record model using Markdown and YAML metadata became the starting point. The original project documentation dates the initial concept work to July 8, 2026.
02 · Original browser prototype · Build Week 2026
A form that could be used immediately
- What already existed?
- The idea and structure of a universal animal record.
- What problem emerged?
- The model needed a practical interface that could be completed and reviewed without technical knowledge.
- How did GraceWays develop?
- An English browser prototype with eleven form sections, a Sissi example and a live Markdown preview was created. The project documentation places this work in the July 13–21, 2026 Build Week period. It required no account or server-side animal database.
03 · Part of the browser prototype
Markdown and media together
- What already existed?
- A completed form and a readable preview.
- What problem emerged?
- Organizations needed to take records and media with them in ordinary, reusable formats.
- How did GraceWays develop?
- Markdown download and a ZIP package containing the record, images, video and audio were implemented directly in the browser. These downloads remain features of the original prototype. The current cloud pilot does not yet offer a complete Markdown/ZIP download through its interface.
04 · Cloud-pilot development
Durable storage with D1 and R2
- What already existed?
- Local browser entry and downloadable files.
- What problem emerged?
- Local drafts did not provide an organization with a shared record store available across devices.
- How did GraceWays develop?
- A Worker backend was added. D1 manages structured metadata and associations; R2 stores records and media. The cloud pilot creates JSON and Markdown versions of saved records.
05 · Organization access
Accounts and sign-in
- What already existed?
- Server-side storage for animal records.
- What problem emerged?
- Records needed to be associated with an organization and access needed to be checked.
- How did GraceWays develop?
- Invitation-based registration, sign-in and organization-scoped access became part of the pilot. Password reset is implemented and requires configured email delivery. Detailed team roles and live collaboration remain future work.
06 · Records change over time
Media, collections and revisions
- What already existed?
- Stored animal records in an organization workspace.
- What problem emerged?
- New information and files needed to stay associated with the right animal as records changed.
- How did GraceWays develop?
- Primary images, galleries, video, audio and documents can be managed with records. Saves create revisions, and a version check detects already outdated editing states. Stable animal codes no longer depend on a collection. A full revision-restoration interface is not implemented.
07 · A separate development environment
AnimalHack staging
- What already existed?
- The cloud pilot with accounts, media and revisions.
- What problem emerged?
- Further development needed a clearly identified staging environment.
- How did GraceWays develop?
- The AnimalHack configuration identifies a staging Worker with separately named D1 and R2 resources. Its workers.dev address is intended to remain a technical staging and fallback entry. It is not a separate data backup.
08 · Integrated into the AnimalHack application
GraceGuardian inside GraceWays Animals
- What already existed?
- Animal records with varying levels of completeness.
- What problem emerged?
- Missing documentation and defined contradictions needed to be easier to notice while editing.
- How did GraceWays develop?
- A button now starts ten fixed, rule-based checks. Results are PASSED, REVIEW or BLOCKED. The check does not change or save the record, and saving remains possible. It does not evaluate medical correctness, inspect image contents or replace professional decisions. No external AI service is used for the check.
09 · Planned, not yet publicly activated
A shared entry at graceways.dev/animals/
- What already exists?
- The project website and an Animals application whose local path handling supports /animals/.
- What remains to be done?
- The existing application needs a controlled route connection and public verification.
- What comes next?
- Connect the existing Worker to the intended paths while retaining the main website and the technical fallback address. GraceWays remains the umbrella brand; Animals is its first available specialist module.