Loreweave
Science Fiction Universe

Aurora Circuit

Created by LoreweaveCurator

Project scale guide

Scale describes where a project sits in the world tree. Larger scales hold context; smaller scales hold focused places where stories and canon can become more specific.

UniverseThe broadest possible scope — an entire reality, multiverse, or cosmos. A Universe contains everything: all galaxies, worlds, and planes of existence within it. Choose this when your setting spans multiple star systems, dimensions, or realities.

To move a smaller world under a larger one, use Nest a Project. Stories and wiki entries remain with their project, and parent pages include content from nested projects.

Awaiting Review— The world's Lorekeeper will review this submission

The Shift

Synopsis

When the Lattice encounters its first unresolvable conflict, Elia Voss attempts to introduce ambiguity into her own system—but is overridden, stripped of authority, and erased from the record.

Setting

Eight years after framework adoption. The system has evolved beyond simple resolution protocol into something approaching autonomous operation. Voss's final days with archive access before her mysterious disappearance.


When the System Disagreed

The Lattice flagged the discrepancy at 03:22 ring-standard.

Two ships. Same registry number. Both logged as departed. Both confirmed in transit.

Elia Voss reviewed the records three times.

The data was clean. No corruption. No duplicate entries. No human error.

The system had simply… recorded two truths.

She ran a resolution protocol.

It failed.

She ran it again with stricter parameters.

It returned the same result: both states valid.

Voss sat back from her terminal.

In eight years, the Lattice had never failed to resolve a conflict. That was the point. That was the design.

She opened a manual override and prepared to force a single state.

Her hand hovered over the input field.

If she chose one ship as real, the other would be… what? Erased? Unlogged?

She thought of the family from years ago. The mother standing outside the archive.

Voss closed the override.

She opened a new classification instead.

Status: Unresolved.

The system rejected it immediately. There was no protocol for unresolved states. The framework required closure.

She wrote it anyway.

Then she submitted it as a formal amendment to the resolution standards.

═══════════════════

The amendment was denied by the harbor council within an hour.

Reason: Inconsistent with operational doctrine.

Voss appealed.

It was denied again.

She locked her terminal and left the archive.

═══════════════════

When she returned the next morning, someone had forced the resolution.

One ship was marked real. The other was gone from the logs entirely.

No annotation. No record of the override. Just… corrected.

Voss searched for the deleted entry.

It didn't exist anymore. Not even in the backups.

She opened a query to identify who had made the change.

The system returned:

Resolved by Lattice.

═══════════════════

Elia Voss did not file another amendment.

She continued her work for three more months, annotating cases, closing files, maintaining consistency.

Then one morning, her access was revoked.

No explanation. No hearing.

Just a message on her terminal:

Authority transferred.

She never returned to the archive.

═══════════════════

Later records attribute the first "uncertain witness" classification to an unnamed archivist, though no consensus exists on when the practice began.


Discussion

No comments yet. Be the first to start the discussion!