Research into decision records for repeated operating choices. Start with a synthetic software-renewal review: dated context, missing facts, human authority and a later outcome still to be observed.
Three subscriptions, one missing deadline, and a question for human review.
Fictional example / Missing information
Example / renewFictional example
Three subscriptions
A fictional small team is reviewing three software subscriptions before an example renewal on 2026-11-05, Europe/Athens. These are scenario dates, not live notices.
Question and context
Which subscriptions still support the team's current work, and what must be checked before the owner decides?
Source dates
Invented usage note: 2026-10-30. Invented renewal notices: 2026-10-29. No provider or account source has been verified.
Decision owner
Fictional operations owner. No actual person is assigned by this website.
Proposed action and approval
Collect current prices, seat use and exit terms. A person must approve any renewal or cancellation; this record changes no account.
Observed outcome
Not observed. A later review would record the decision, actual cost and operational effect. No savings, causation or transferability has been established.
Supplied information
01Service A has no use recorded in the sample's last 30 days; its sample notice includes renewal and cancellation deadlines.
02Service B is used regularly and offers monthly or annual terms; its sample notice includes renewal and cancellation deadlines.
03Service C's renewal notice says the price will change and includes its renewal deadline. Cancellation deadline: Not supplied.
Criteria
Cost
Recent use
Alternatives
Deadline
The person's rules
Unresolved in this example
The deadline for changing Service C is missing.
For human review
Check that deadline before assuming there is time to change the renewal.
Limits of this example. Real subscriptions, prices and current provider terms have not been checked. Absolute dates belong to this synthetic scenario. No actual renewal is scheduled by the record.
Fictional example. No account, order or payment is changed.
A missing deadline remains a question, not a confident answer.
A choice can depend on information held in different places: a provider's terms, a person's preferences, a deadline. Omega explores how those facts could be presented together, with their sources and limits visible.
The proposal is a review layer between information and action. This website demonstrates its possible shape.
A concept website, fictional records and a proposed review flow.
What needs testing
Whether a dated record improves retrieval, follow-up or a later decision compared with ordinary notes or the current assistant workflow.
Longer-term questions
How should context and later outcomes be compared without assuming causation or transferability? Provider portability, cryptographic verification and a recipe marketplace remain unproved later directions.
Help define a useful decision record.
Reviewing repeated software renewals, workflow priorities or another consequential operating decision? Describe one situation where the inputs or approval rules are difficult to inspect.
Prepare an email draft to review and send from your own inbox.
Questions about the concept.
What exists today?+
This concept website, fictional decision records and an email enquiry route.
Is this a bank, payment service or AI product?+
Omega is the method and research layer for decision records. ODM is the proposed pilot experience; Smoltie may later provide task-facing helpers. The examples connect no accounts, run no model and carry out no action.
What is LemmyPay?+
A worked illustrative comparison in the same decision family, not a separate live financial-service proposition.
Who makes the decision?+
A person reviews the example's facts and questions. Any future delegation would need explicit authority, limits and an exception path.
When will it be available?+
No release date or access offer is confirmed. You can prepare an email to request updates.
Who can contribute?+
Operators, design partners and researchers can describe one repeated review decision through the partner enquiry. Existing internal pilot work retains its separate scope.