record
Let an agent handle financial records by type, content, retention, integrity and access, and treat them as evidence.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Researched by: Claude
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Content What it records.
Entries
Transactions.
Entries
Recorded transactions.
- What transactions does it record? definition
- With which dates and amounts? measurement
Type
Ledger, receipt.
Type
Record type.
- What type of record is it? definition
- Who issued it? provenance
Integrity Trustworthiness.
Audit trail
Changes.
Audit trail
Change history.
- Is there an audit trail of changes? provenance
- Who can edit? boundary
Authenticity
Genuine.
Authenticity
Authenticity checks.
- Is the record authentic? boundary
- How can it be verified? action
Retention How long.
Period
Legal minimum.
Retention
Retention period.
- How long must it be kept? boundary
- Under which law? provenance
Disposal
Secure deletion.
Disposal
Disposal.
- How should it be disposed of securely? action
- When? boundary
Access Who sees it.
Access rights
Permissions.
Access
Access control.
- Who may access these records? boundary
- Is access logged? provenance
Evidence
In disputes.
Evidence use
Use as evidence.
- Can it be used as evidence in a dispute? boundary
- What form is required? definition
Classifiers Filled
- Family
- Thing Registry
- Category
- Society, people and institutions
- Entry kind
- noun.possession
- Plane
- SOC
- Domain
- SOC.ECO
- Facets: substance
- social
- Facets: origin
- conceptual
- Facets: agency
- inert
- Facets: mobility
- not-applicable
- Facets: scale
- not-applicable
- Facets: affordances
- observable
- Also called
- balance sheet, expense record, ledger, leger, account book, book of account, book, cost ledger, general ledger, subsidiary ledger, control account, daybook
What it is Filled
A document or entry that can serve as evidence of a transaction or account, such as a ledger, account book, receipt or balance sheet.
Why it exists Filled
Let an agent handle financial records by type, content, retention, integrity and access, and treat them as evidence.
Distinguishing features Filled
- Evidence of transactions
- Retention periods set by law
- Integrity and audit trails matter
- A sports record is a different sense
What robots and AI may and may not do Derived, awaiting review
May
- create and keep records
- retain them for legal periods
- audit them
- produce them as evidence
Note: Affordances listed as what may be done; prohibitions collected from the text.
Moral aspects Derived, awaiting review
- Data protection for personal data in records
Owners Missing, in the backlog
Not described yet. This gap is in the card backlog.
Links to other meta-models Filled
parent
- oewn-13424504-n - registry parent class
related
- document - evidence
- payment and transaction - content
- record as achievement - a homonym
- auditor - check
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- document number: system-specific invoice or voucher numbers
Direct properties not applicable Not applicable
Not applicable
Plane SOC: no invented physical properties.
Recognition optional Filled
- Dated entries with amounts and parties
- Account books and ledgers
- Digital accounting records
- Ledgers, receipts, statements and accounting system entries.
Capabilities and actions required Filled
- create and keep records
- retain them for legal periods
- audit them
- produce them as evidence
Hazards and failure modes required Filled
- Lost or altered records
- Keeping records longer than lawful
- Fraudulent records
Standards and interfaces required Filled
- Record retention law for tax and accounting
- EU e-invoicing rules
- Data protection for personal data in records
Context of use required Filled
- Evidencing transactions and keeping accounts.
- ledgers and account books
- receipts and invoices
- bank statements
- balance sheets and expense records
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Written from model knowledge without web access; claims are unverified.
Open questions
- Should record types be separate entries?
- How should retention periods be linked by country?
- How should integrity be verified?
- How can it be verified?
- How should it be disposed of securely?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-record-possession/spec.json