Resolution Immutability

Once a resolution is created in Decisio, it becomes a permanent record. This immutability is a core design principle that ensures the integrity of your decision-making history.

Why immutability matters

Mutable records undermine trust. If past decisions can be quietly altered or deleted, the audit trail loses its evidentiary value. Decisio's immutability guarantee ensures:

• Accountability: Decisions cannot be hidden or revised after the fact

• Legal defensibility: Records reflect what actually happened, not a sanitized version

• Regulatory compliance: Auditors can trust that records are authentic

• Organizational memory: Historical decisions remain accessible and unchanged

How immutability works

Resolutions are permanent

When a motion passes and creates a resolution, that resolution becomes a permanent fixture in your workspace. The record includes:

• The exact motion text that was resolved

• All votes cast and by whom

• The timestamp of resolution

• Any exhibits that were attached

None of these elements can be edited or removed after the resolution is created.

Voiding preserves history

Sometimes decisions need to be reversed. Rather than deleting the original resolution, Decisio creates a voiding record:

Original resolution	Voiding action
Remains in full	New record created
Marked as voided	References the original
Timestamp preserved	New timestamp recorded
All votes visible	Voiding user attributed

This approach maintains the complete history while clearly indicating that a decision has been reversed.

Superseding maintains lineage

When a new decision replaces an old one, Decisio creates a superseding relationship:

1. The original resolution is marked as superseded

2. A new resolution is created for the replacement decision

3. Both records link to each other

4. The full history of the decision evolution is preserved

This is particularly valuable for policies or standing decisions that evolve over time.

What cannot be changed

Once a resolution exists, the following are immutable:

• Resolution content: The text of the decided motion

• Vote records: Who voted, how they voted, and when

• Timestamps: When events occurred

• User attribution: Who took which actions

• Exhibits: Documents attached at the time of resolution

What can be done

While the resolution itself is immutable, you can:

• Void a resolution: Creates a new record indicating the decision was reversed

• Supersede a resolution: Creates a new decision that replaces the old one

• Add comments: Annotate resolutions with additional context

• Export records: Download resolution data for external use

The voiding process

To void a resolution:

1. Navigate to the resolution

2. Click Void Resolution

3. Provide a reason for voiding (required)

4. Confirm the action

The voiding action creates a new timestamped record that:

• Links to the original resolution

• Records the user who voided it

• Captures the stated reason

• Updates the resolution status to "Voided"

The original resolution content remains fully visible and accessible.

The superseding process

To supersede a resolution:

1. Create a new motion addressing the same matter

2. In the motion, reference the existing resolution

3. Conduct voting as normal

4. When the new motion passes, it supersedes the original

The new resolution automatically links to its predecessor, creating a clear chain of decision evolution.

Audit implications

Immutability has important implications for audits:

What auditors see

• Complete, unaltered records of all decisions

• Full visibility into voided and superseded decisions

• Clear attribution for all actions

• Accurate timestamps for the entire lifecycle

What auditors can verify

• Decisions were made through proper process

• Changes to decisions are documented and explained

• No records have been tampered with or deleted

• The decision-making timeline is authentic

Technical implementation

Decisio's immutability is enforced at the database level:

• Resolution records use append-only storage patterns

• Deletion operations are not available for resolution data

• Modification triggers create new records rather than updating existing ones

• Timestamps are server-generated and cannot be user-modified

Best practices

To work effectively with immutable records:

• Review before resolving: Once created, a resolution cannot be edited, so verify accuracy first

• Use voiding sparingly: Frequent voiding may indicate process issues that should be addressed

• Document superseding clearly: When replacing a decision, explain why in the new motion

• Maintain context: Since resolutions are permanent, ensure they contain sufficient context to be understood later

Next steps

• Audit Trail Overview - Understand the complete audit trail

• Export and Reporting - Learn about accessing your records

• Data Privacy - Review our data handling practices