Updating FateLoom…
⚠
Version
Plan and explore interconnected timelines directly in your browser.
Made with ❤️ and 100% open source. FateLoom and its source code are available under GNU AGPLv3.
For proprietary integrations or modified network services that cannot meet the AGPLv3 source-sharing requirements, choose a Commercial License.
FateLoom was designed and directed by a human. Generative AI assisted extensively with source code and documentation; human review and release responsibility remain with the project owner. FateLoom itself does not run an AI model or make automated inferences. This provenance notice is not a legal classification or compliance declaration under Regulation (EU) 2024/1689 (EU AI Act).
Stored calendar data could not be opened safely
FateLoom kept the original browser data unchanged and opened the demo calendar in read-only recovery mode.
Navigation, gestures, and keyboard shortcuts
Select a calendar. Double-click or press Enter to open it.
Adjacent sheets repeat the overlap area for trimming and alignment.
Privacy takes effort from everyone who values it—and every practical step is worth taking.
Using private browsing? FateLoom deliberately does not try to detect it. Browser storage is temporary in private sessions and is normally deleted when the session ends, often when every private window closes. Export your calendars before leaving.
FateLoom stores every calendar only in this browser. There is no account or cloud sync.
Standard browser storage can be removed automatically when space is low. Persistent storage asks this browser to protect FateLoom data from that automatic cleanup.
You can still remove the data from browser settings or by deleting the browser profile. Use Export all in Calendar Manager and Import from File as a portable backup.
Open the site controls beside the address bar, reset or allow persistent storage for this site, reload FateLoom, then request protection again. Browser labels vary.
In Firefox: open the padlock, choose Connection, More information, Permissions, then allow persistent storage.
Use ${NAME} in item titles and numeric amount fields. Global variables also work in verification messages. They are saved in the current calendar JSON and travel with Export calendar. Copy inserts the complete token.
${NAME}
Use ${NAME} in this item's title and verification messages. Set an alias to reference its variables elsewhere as ${ALIAS.NAME}. Copy inserts the complete token.
${ALIAS.NAME}