[corpospec]
Governance pillar · v0.8.1

resolution Resolution

Formal corporate resolution (e.g. Gesellschafterbeschluss under § 48 GmbHG).

$id · https://corpospec.com/schemas/v0.8.1/resolution.schema.json

View raw JSON → ← all schemas

Fields

Field Type Required Description
date IsoDate yes ISO 8601 date (YYYY-MM-DD).
decision_makers PathRef[] yes
entity PathRef yes Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
id PathRef yes Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
items ResolutionItem[] yes
procedure ResolutionProcedure yes Voting procedure for a corporate resolution.
legal_basis string? — Statutory or contractual basis authorising the resolution. For German GmbH Gesellschafterbeschluesse this is typically a section of the GmbHG (e.g. "§ 48 GmbHG" for shareholder resolutions, "§ 46 GmbHG" for the shareholder competence catalogue, "§ 49 GmbHG" for the convocation of meetings). For other jurisdictions cite the relevant statute (e.g. "Delaware General Corporation Law, Title 8, Chapter 1"). Kept as free-form string to accommodate cross-jurisdiction prose.
related_contracts PathRef[] —
related_decisions PathRef[] —
retention_years integer? — Minimum retention period in years under applicable law. Under German commercial and tax law, shareholder resolutions qualify as accounting records under § 257 HGB and § 147 AO with a 10-year retention duty; foundational instruments (incorporation, capital changes) are typically retained for the lifetime of the entity (often encoded as 99). The value is advisory — enforcement lives in the retention policy, not the schema.

Definitions

Shared types referenced within this schema.

IsoDate
ISO 8601 date (YYYY-MM-DD).
type: string
PathRef
Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
pattern: ^[a-z0-9_-]+(/[a-z0-9_.-]+)+$
ResolutionItem
A single item within a corporate resolution. The `number` ordering is document-scoped and expected to be unique per resolution; uniqueness cannot be expressed in JSON Schema and is enforced at validation time.
type: object
ResolutionOutcome
Outcome of a single resolution item.
enum: "approved", "rejected", "deferred", "withdrawn"
ResolutionProcedure
Voting procedure for a corporate resolution.
enum: "written_circular", "meeting"

Reference in your YAML

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.8.1/resolution.schema.json