Credit / Security
Connect separately mastered financial instruments, positions, obligations and security rights through a typed, evidenced reference pattern.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 36 questions
Scope and classification Context for scope and classification in a typed reference application.
Typed subject routing
Choose the subject role before attaching records; a security instrument is not its holding or a collateral right.
Typed subject routing
Choose the subject role before attaching records; a security instrument is not its holding or a collateral right. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which record role and classification profile apply to this reference? classification
- Which debt, equity, contingent or hybrid features require a separate specialist profile? constraint
- Which successor binding owns each financial record in this application? composition
Applicable interpretation
Record the context in which a term is interpreted without turning a statistical category or model law into a legal conclusion.
Applicable interpretation
Record the context in which a term is interpreted without turning a statistical category or model law into a legal conclusion. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which jurisdiction and competent authority support the asserted legal interpretation? authority
- Does security here denote an instrument, a collateral right or another meaning requiring rejection? definition
- Which asset or transaction falls outside the selected classification or secured-transactions profile? exception
Identity and parties Context for identity and parties in a typed reference application.
Qualified identifier bindings
Keep local master identifiers and external identifiers with their schemes, scope and verification status.
Qualified identifier bindings
Keep local master identifiers and external identifiers with their schemes, scope and verification status. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which master identifier resolves the instrument independently of its holder position? identity
- Which external identifier scheme and version qualify each identifier? interoperability
- Which ambiguous or conflicting identifier mappings must remain unresolved? quality
Party and stewardship links
A party can have distinct issuer, obligor, holder, custodian or grantor roles; local stewardship grants no financial entitlement.
Party and stewardship links
A party can have distinct issuer, obligor, holder, custodian or grantor roles; local stewardship grants no financial entitlement. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which separately identified parties occupy the issuer, obligor, holder and intermediary roles? relationship
- Which steward controls this manifest and which masters control the referenced financial records? ownership
- Which documented entitlement permits the recipient to see a party or position reference? access
Instrument and position views Context for instrument and position views in a typed reference application.
Referenced economic terms
Store a selected observation of externally mastered terms, including residual equity rights, with basis and time.
Referenced economic terms
Store a selected observation of externally mastered terms, including residual equity rights, with basis and time. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which authoritative instrument revision supports the displayed terms? evidence
- Which currency, quantity unit and value basis qualify each displayed amount? measurement
- Which maturity, coupon or repayment fields are inapplicable to the selected equity or perpetual instrument? constraint
Position observation
Reference an as-of holding separately from an issuance total or an obligation; discrepancies remain explicit.
Position observation
Reference an as-of holding separately from an issuance total or an obligation; discrepancies remain explicit. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which position master and account context identify this holding observation? identity
- At which trade, settlement or reporting basis is the position observed? temporal
- Which double-counted, missing or conflicting position observations prevent reconciliation? validation
Lifecycle and flow references Context for lifecycle and flow references in a typed reference application.
Obligation and payment evidence
Link separately mastered schedules and payment evidence without equating accrual, due amounts and settled payments.
Obligation and payment evidence
Link separately mastered schedules and payment evidence without equating accrual, due amounts and settled payments. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which obligation and schedule versions are relevant to this instrument view? composition
- Which evidence supports a due, paid, disputed or externally asserted default status? state
- Which payment or settlement records reconcile a scheduled amount without authorizing payment execution? process
Lifecycle and corporate-action linkage
Represent the relationship between external event versions and affected references; do not execute corporate actions.
Lifecycle and corporate-action linkage
Represent the relationship between external event versions and affected references; do not execute corporate actions. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which external issuance, amendment, conversion or corporate action affects these references? event
- Which announcement, effective and observation times apply to the change? temporal
- Which successor reference or residual claim remains after redemption, maturity or cancellation? lifecycle
Collateral and valuation links Context for collateral and valuation links in a typed reference application.
Security-right context
Link assets, obligations and asserted security rights with evidence of scope; a local link is not creation, perfection, priority or enforcement.
Security-right context
Link assets, obligations and asserted security rights with evidence of scope; a local link is not creation, perfection, priority or enforcement. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which security-right master links which assets and secured obligations? relationship
- Which legal profile and external evidence support the asserted effectiveness or priority? authority
- Which competing right, excluded asset or missing evidence makes collateral status unresolved? exception
Valuation observation context
Keep external valuation observations and contractual adjustments distinguishable from the existence or legal strength of a security right.
Valuation observation context
Keep external valuation observations and contractual adjustments distinguishable from the existence or legal strength of a security right. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which external valuation, currency and as-of time support the displayed collateral amount? measurement
- Which source and profile support a haircut or coverage calculation used in this view? provenance
- Which stale, disputed or incomparable values prevent a coverage assertion? quality
Evidence and controlled exchange Context for evidence and controlled exchange in a typed reference application.
Evidence continuity and retention
Keep attribution and revision links while applying the adopting profile to sensitive payload retention and correction.
Evidence continuity and retention
Keep attribution and revision links while applying the adopting profile to sensitive payload retention and correction. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which evidence entity, activity and responsible role produced each local observation? provenance
- Which retention period, legal hold or approved disposition applies to the local evidence payload? retention
- Which correction or erasure can be recorded without claiming to erase an external financial obligation? privacy
Versioned projection and release
Exchange only qualified reference projections under a selected message profile and recipient policy.
Versioned projection and release
Exchange only qualified reference projections under a selected message profile and recipient policy. This is a proposed local design informed by the cited source scope, not a source-mandated data schema.
- Which exact message definition and mapping version represent this projection? interoperability
- Which purpose and recipient permissions constrain the projection at every structural scope? security
- Which reference, version or disclosure checks must pass before releasing the local view? validation
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- pattern
- Navigation path
- NAV.SOC.ECO.INS2
- Domain
- SOC.ECO.INS2
- Industry
- Cross-industry
- Tags
- creditsecuritysoc.eco.ins2
- Also called
- F8
What it is Filled
A reusable reference-composition pattern resolving the legacy F8 category. An application is a versioned manifest of references and observations, not a financial instrument, portfolio ledger, security right or financial transaction. Security means financial securities or collateral rights, not physical or cyber security.
In scope
- Typed routing and identity bindings for loans, debt securities, equity instruments, holdings, obligations and collateral rights.
- Evidence-backed reference snapshots, interpretation constraints and reconciliation of legacy fields.
- Local manifest revisions, applicability profiles and recipient-specific projections.
Out of scope
- Master instrument terms and lifecycles owned by debt or equity instrument profiles; holdings and entitlement ledgers owned by position profiles.
- Payment execution, trading, custody, settlement finality, collateral creation or enforcement, credit scoring, lending decisions and investment advice.
- Legal determination of default, title, priority, regulatory capital, tax or accounting recognition; derivatives and guarantees require separate profiles.
- Universal security classification, property appraisal and source-system audit execution.
Why it exists Filled
Connect separately mastered financial instruments, positions, obligations and security rights through a typed, evidenced reference pattern.
Distinguishing features Derived, awaiting review
- Unlike WM-ECO-037 Debt Instrument: Incoming candidate EXTEND relation remains a specialization proposal. Debt identity, terms and cashflows are referenced; this pattern does not duplicate their master lifecycle.
- Unlike WM-ECO-038 Equity / Security Holding: Incoming candidate EXTEND relation does not collapse an equity issue into an investor holding. Position and instrument references are distinct; debt holdings may also use a qualified position profile.
- Unlike Agreement, money, party and collateral asset masters: Use qualified references. No agreement record is universally mandatory, no identifiers prove authority and no linked collateral record changes asset ownership.
- Unlike Legacy F8 and unreviewed supplement: Input leads only. Reject universal bilateral visibility, debt-like equity obligations, maturity-implies-closure, a single repayment schedule and universal collateral-without-title-transfer assertions.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Default deny for sensitive position and party data; expose only the minimum needed for the recipient purpose.
- External financial-record deletion and retention execution belong to source owners and approved storage services; local deletion cannot discharge debt or release collateral.
- Deny unless an explicit role, purpose and subject scope authorize reading or modification; bilateral participation is not blanket access.
May
- Classify a reference: Proposed, unimplemented local operation. Record a proposed routing decision only.
- Bind qualified identifiers: Proposed, unimplemented local operation. Create a versioned local mapping; do not alter source identifiers.
- Record an as-of reference view: Proposed, unimplemented local operation. Record an observation with provenance, not a new financial position.
- Inspect link consistency: Proposed, unimplemented local operation. Record local exceptions; do not settle, default, transfer or enforce.
- Build a permitted projection: Proposed, unimplemented local operation. Generate a local recipient view with losses declared; no external transmission.
- Retire a local manifest revision: Proposed, unimplemented local operation. Retire local references and dispose approved payloads; no cancellation of financial rights.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Preserve only lawful minimal tombstones, not indefinite personal data history.
- ICO guidance is a UK privacy example; local adoption needs current law and sector-specific retention review.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Adopting Dimension identifies an accountable steward role and the namespace authority.
Roles
- Manifest steward
- Approve local purpose, namespace and profile selection.
- Evidence curator
- Record qualified references and source limitations.
- Financial subject reviewer
- Resolve domain interpretation without executing transactions.
- Access and retention reviewer
- Authorize recipient views and lawful local disposition.
- Audit reader
- Inspect permitted provenance and unresolved holds without changing records.
Links to other meta-models Filled
references
- WM-ECO-037 - Candidate incoming EXTEND specialization consumes the pattern; reference debt masters without reversing the candidate into mandatory containment. Version binding deferred.
- WM-ECO-038 - Candidate incoming EXTEND specialization consumes the pattern; holding masters remain separate from instrument masters. Version binding deferred.
- Agreement and party profiles - Select governed agreement, issuer, holder, obligor and intermediary references as applicable; registry IDs and versions require profile review.
- Money and settlement profiles - Link payment and settlement evidence; leave execution and finality in the source profile.
- Collateral asset and security-right profiles - Identify assets and rights separately; leave creation, valuation, priority determination and enforcement outside this pattern.
aligned
- ISO 20022 - Select and test versioned message mappings; catalogue access alone establishes no conformance.
- FIGI 1.0 and LEI - Qualified instrument and legal entity identification alignments; no ownership or authority inference.
- W3C PROV-O - Conceptual evidence attribution and derivation; mapping and conformance remain deferred.
neighbor
- WM-ECO-037 Debt Instrument - Incoming candidate EXTEND relation remains a specialization proposal. Debt identity, terms and cashflows are referenced; this pattern does not duplicate their master lifecycle.
- WM-ECO-038 Equity / Security Holding - Incoming candidate EXTEND relation does not collapse an equity issue into an investor holding. Position and instrument references are distinct; debt holdings may also use a qualified position profile.
- Agreement, money, party and collateral asset masters - Use qualified references. No agreement record is universally mandatory, no identifiers prove authority and no linked collateral record changes asset ownership.
- Legacy F8 and unreviewed supplement - Input leads only. Reject universal bilateral visibility, debt-like equity obligations, maturity-implies-closure, a single repayment schedule and universal collateral-without-title-transfer assertions.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier with namespace
- Governed global identifier or IRI
- UUID or ULID assigned by the adopting Dimension
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Classify a reference: Proposed, unimplemented local operation. Record a proposed routing decision only.
- Bind qualified identifiers: Proposed, unimplemented local operation. Create a versioned local mapping; do not alter source identifiers.
- Record an as-of reference view: Proposed, unimplemented local operation. Record an observation with provenance, not a new financial position.
- Inspect link consistency: Proposed, unimplemented local operation. Record local exceptions; do not settle, default, transfer or enforce.
- Build a permitted projection: Proposed, unimplemented local operation. Generate a local recipient view with losses declared; no external transmission.
- Retire a local manifest revision: Proposed, unimplemented local operation. Retire local references and dispose approved payloads; no cancellation of financial rights.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- ISO 20022 Message Definitions
- PROV-O: The PROV Ontology
Context of use required Filled
- IMF and securities statistics guidance is conceptual statistical evidence, not private-law authority.
- UNCITRAL is a model-law example for selected movable property, not universal enacted law or land security law.
- ICO guidance is a UK privacy example; local adoption needs current law and sector-specific retention review.
Sources Filled
- Monetary and Financial Statistics Manual and Compilation Guide - International Monetary Fund
- Handbook on Securities Statistics - Bank for International Settlements; European Central Bank; International Monetary Fund
- UNCITRAL Model Law on Secured Transactions - United Nations Commission on International Trade Law
- The Legal Entity Identifier - Global Legal Entity Identifier Foundation
- ISO 20022 Message Definitions - International Organization for Standardization
- Financial Instrument Global Identifier specification - Object Management Group
- PROV-O: The PROV Ontology - World Wide Web Consortium
- A guide to the data protection principles - Information Commissioner Office
Open questions
- Run and review coordinator source HTTP measurements, source versions, errata, licenses and source-specific claim support; retain retrieval failures without treating status success as substantive verification.
- Pin and test successor and master bindings with equity, perpetual debt, unsettled holdings, disputed default, multiple schedules, competing collateral claims and lawful local disposal cases.
- Review hybrid, contingent, derivative, guarantee, securitization, beneficial ownership and title-transfer profiles without widening this pattern into their financial masters.
- Restore independent external review and resolve legal and conformance holds before any canonical or publishable-draft promotion.
- Executable nested schemas, binding versions and adversarial instance fixtures are not implemented.
- Derivatives, guarantees, Islamic finance, securitization, beneficial ownership chains and title-transfer collateral need specialist profiles.
- Current legal applicability, source versions, licensing and independent external review remain unverified.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-eco-005-credit-security/spec.yaml