Features
Collect and connect records,
built to use them again
Explore work recorded in diaries and wikis through time and context.
01 Search and reading
Go beyond summaries
and open the source directly
Search titles, bodies and keywords, then read the original from the results. Jump directly to the line you need in long documents.
- See matches in titles, bodies, keywords, aliases and classifications, with surrounding context.
- Open documents from results and follow body links to related records.
- Find in document (Ctrl+F), contents navigation and source line-number navigation are supported.
- Keep documents in tabs and switch quickly with (Alt+←/→).
Weekly operations meeting
Distribution center Night dispatch pilot will be extended by two weeks.
Body · Line 9Night dispatch pilot results
The next-day arrival rate improved from 91% to 97%.
TitleLogistics staffing plan
Night dispatch requires one additional staff member
Reference document
02 Time views and schedules
See what happened when
along a timeline
Explore events and schedules over time alongside their linked sources.
- The dashboard separates dated events and schedules from documents for continued reference.
- Open records to read their contents and use linked evidence to find source locations.
- Dates come from events and meetings actually recorded in documents, not file modification times.
Directly authored records need not have a source document. Passing a scheduled date does not automatically create an actual event.
Dates versus schedulesFinal decision on extending night dispatch
Weekly operations meeting
Prepare price changes compared with Q2
Supplier price negotiation
Release receiving inspection checklist v3
Weekly operations meeting
03 Team archives
Share team materials with the right permissions,
restore earlier versions when edits go wrong
Use independent personal and organization archives, with access clearly separated by member role.
- Owners invite teammates by email address; teammates review and accept in the app.
- Owners and editors can read and edit; viewers can only read.
- Review document history by revision and restore an earlier version.
- Share links to document locations; the recipient’s permission is checked on every read.
Before sharing
No invitation email is sent. Tell teammates directly to accept with an Alfred account whose verified email matches the invitation.
Restoring needs retained history and edit permission. Deleting or emptying an archive cannot be undone.
Alfred 3×5
Different views of the same record
- 2 record areas
- Record in diaries and wikis.
- 3 time views
- Explore the past, present and future.
- 5 browsing axes
- Link by period, relationships, projects, resources and topics.
Body links differ from group membership. To gather and count records in a group, explicitly connect them to that classification.
Organization and links guideSecurity and privacy
Your work records matter:
archives are encrypted and permissions checked every time
Record bodies and revision history stored on the server are encrypted, with permission checked on each access.
Some control metadata, such as accounts, sessions, organizations and permissions, is stored separately. This is encryption at rest: the server decrypts authorized requests, not end-to-end encryption (E2EE) that prevents the server reading content. It does not guarantee encryption of local archives or downloaded backups.
- We do not store passwords
- Sign in through your social account without giving us a password. Sign-in lasts 30 days; signing out immediately ends the server session.
- Permission is checked every time
- Existing AI connections cannot access archives after permission is revoked.
- You approve AI connections
- Connections use OAuth 2.1 and PKCE, with separate read and write approvals. The authorization page clearly shows the permitted operations.
- Document bodies stay out of access logs
- Access logs contain operational details such as request type and outcome, not document bodies, search terms, file paths or authentication tokens.