Authority Gap

Mapping authority, participation, records, and outcomes across systems.

A documentation project built to show where authority lives, where participation breaks down, and how records, notice, and outcomes connect across institutions.

Research Archive

Evidence, documents, and source-indexed notes.

Archival material sits at the center of the project so every next step can be traced back to source material.

ARCHIVE

Source index

Documents, emails, notices, and public records.

Records are grouped by source, date, and issue so the archive stays navigable.

MAP

Evidence map

What each record proves, suggests, or leaves open.

DOCS

Documentation library

Research notes and reference packets.

Short summaries keep the archive useful when the same topic comes up again.

FILES

Records library

Named, dated, and organized for review.

Timeline Explorer

A record of events, notices, responses, and gaps.

The timeline layer is meant to show sequence without hiding uncertainty. Events stay connected to the source that established them.

  • Notice received and categorized
  • Responses logged with date and sender
  • Missing records marked as open items
  • Follow-up entries linked to source documents

Minimal diagram

Connected nodes, not isolated facts.

01Input

Record arrives.

02Sort

Place into timeline.

03Test

Check authority.

04Track

Mark what remains open.

Authority Stack Visualizer

Who decides, who participates, and what record supports it.

Authority

Where power sits.

Identify the office, person, or process controlling the answer.

Participation

Who was included.

Track notice, access, response windows, and practical participation.

Outcome

What happened next.

Link the record to the result so the chain of events stays visible.

Open Questions Registry

Questions, owners, and status, kept in the open.

  • What is known from source documents
  • What remains unanswered or disputed
  • Which office or person controls the next answer
  • What follow-up step is already due

Public Records Tracking

Requests, responses, delays, and delivery.

RequestsLogged

Dates and topics are recorded.

ResponsesTracked

Partial and complete replies stay visible.

DeadlinesMonitored

Follow-ups are tied to the timeline.

StatusClear

Each request has a current state.

Educational Resources

References designed to help the record make sense.

Case studies

Concrete examples of how the framework is used.

Short, source-oriented writeups that make the system easier to learn.

Documentation library

Templates for intake, tracking, and review.

Reusable structure for documents, notes, and follow-up steps.

Timeline tools

Ways to sort and compare records fast.

Useful when the same event appears in multiple formats.

Source notes

Short annotations tied to each item.

Helps keep the archive useful after the first pass.

Visit Authority Gap

Open the project and move through the evidence layer.

Use the archive, timeline, and question registry together to keep the structure intact.