Projects · Information & Digital Systems

Information & Digital Systems

Examine how platforms, algorithms, automated decisions, synthetic media, ranking systems, repetition, personalization, source quality, and digital interfaces shape what citizens see and what they come to believe.

Explore the ProjectSystems of Trust
Project Principle
A system can influence a conclusion without issuing a command. Visibility, ranking, repetition, omission, personalization, and friction can all shape the informational environment in which citizens decide what is true or important.

Projects are where the framework becomes testable against real systems. This project uses Public Knowledge to establish the knowable basis, Systems of Trust to examine conduct and structure, and Citizen Agency to choose and navigate an informed course.

Project Focus

What this project examines.

The project is organized around recurring system questions rather than a single dispute or predetermined conclusion.

Source Provenance

Identify original sources, derivative summaries, screenshots, reposts, edits, missing context, and the path by which information reached the citizen.

Algorithms & Ranking

Examine how search, recommendation, feeds, ranking, moderation, and personalization affect visibility and attention.

Synthetic Media

Distinguish authentic records from generated, altered, edited, or context-shifted media and preserve uncertainty when provenance cannot be established.

Automated Decisions

Study systems that score, classify, recommend, deny, prioritize, flag, or route people and the records needed to test those outputs.

Interface & Choice Architecture

Examine defaults, prompts, friction, warnings, consent flows, dark patterns, and other design choices affecting meaningful agency.

Public Knowledge Online

Develop practical methods for source verification, proposition status, correction, and independent inspection in high-volume information environments.

Public Knowledge

What must become visible.

Before the system can be tested, the relevant authority, factual record, standards, practices, decision record, claims, and unresolved questions must be distinguished.

What governs?Applicable statutes, contracts, platform rules, privacy requirements, consumer protections, agency guidance, and judicial authority.
What happened?Inputs, outputs, source history, timestamps, versions, prompts, notices, account actions, recommendation paths, and available logs.
What should happen?Published policies, moderation rules, model documentation, professional standards, data-governance practices, and disclosure commitments.
How does the system operate?Collection, ranking, classification, recommendation, personalization, filtering, moderation, generation, logging, and appeal workflows.
How was the decision produced?What inputs and rules contributed to the output, what human review occurred, what explanation exists, and what can be independently tested.
What remains unresolved?Unknown training or ranking factors, unavailable logs, uncertain provenance, disputed authenticity, opaque scoring, unexplained moderation, or missing context.
Applied Systems of Trust

Examine conduct and architecture separately.

The purpose is not to label a system trustworthy or untrustworthy. It is to examine what the available record supports, what remains unresolved, and what degree of trust or reliance the citizen is justified in extending.

Conditions of Trustworthiness

Ask what observed conduct supports, undermines, or leaves unresolved about Sincerity, Reliability, Commitment, Integrity, Competence, and Consistency.

Conduct Test

Keep the factual proposition separate from the broader inference. One event may bear on a condition without establishing a system-wide conclusion.

Trust Architecture

Ask whether Evidence, Transparency, Defined Duty, Independent Check, Accountability, and Remedy make consequential decisions visible enough to test, trace, review, and correct.

Structural Test

Architecture does not command confidence. It gives the citizen concrete questions for deciding what degree of reliance the known record justifies.

System X-Ray

Work backward from the consequential result.

Begin by naming the consequential question. Then use the same nine questions to examine a single event, institutional workflow, recurring practice, or proposed reform.

Preliminary Step · Name the consequential question.Define the consequential decision, claim, right, obligation, or institutional output being examined.
1 · What governs?Applicable statutes, contracts, platform rules, privacy requirements, consumer protections, agency guidance, and judicial authority.
2 · What happened?Inputs, outputs, source history, timestamps, versions, prompts, notices, account actions, recommendation paths, and available logs.
3 · What should happen?Published policies, moderation rules, model documentation, professional standards, data-governance practices, and disclosure commitments.
4 · How does the system actually operate?Collection, ranking, classification, recommendation, personalization, filtering, moderation, generation, logging, and appeal workflows.
5 · How was the decision produced?What inputs and rules contributed to the output, what human review occurred, what explanation exists, and what can be independently tested.
6 · What remains unresolved?Unknown training or ranking factors, unavailable logs, uncertain provenance, disputed authenticity, opaque scoring, unexplained moderation, or missing context.
7 · Who independently checks the decision?Identify who can test the facts, reasoning, compliance, or result independently of the person, role, workflow, or institution that produced it, and what record of that review exists.
8 · Who is accountable?Identify the responsible decision makers, roles, duties, institutional ownership, and where responsibility for the consequential conduct or result can be traced.
9 · What remedy exists?Identify correction, reconsideration, appeal, compensation, disclosure, enforcement, reform, or another available remedy.
Project Outputs

Research should produce usable public knowledge.

Current and Planned Outputs

  • Citizen source-verification guides
  • Digital System X-Ray examples
  • Synthetic-media and provenance explainers
  • Automated-decision case studies
  • Public Knowledge standards for online sources
  • Research on interface design, ranking, and citizen agency

Citizen Agency — Navigation

  • Trace consequential claims back toward their original source.
  • Separate repetition and popularity from verification.
  • Preserve screenshots, URLs, dates, versions, and context when a digital record may change.
  • Ask what inputs produced an automated decision and what review is available.
  • Keep unresolved provenance or model behavior labeled as unresolved.
See clearly. Ask what matters. Verify what is true. Understand the system. Choose your course. Act with purpose. Check your position.After a meaningful step, ask: What changed? What remains? Are you closer to resolution or recovery?
HOLD COURSE · CORRECT COURSE · CHOOSE A NEW COURSE
When the way forward is unclear, confirm what is true, identify what remains unresolved, and look for the rest of the story.
Project Status

Living public-interest research

This page defines the project's scope and method. Individual white papers, authorities, case studies, practical guides, and reform materials should remain separately sourced and may be revised as authority, records, or institutional practice change.

The Public Method

Learn what governs. Examine the relevant facts. Distinguish what is known from what remains unresolved. Test the system to reach informed conclusions. Decide where trust is justified, then choose an informed path forward.

Continue

Follow the sources or continue the framework.

Use the related pages below to move from this project overview into Public Knowledge, legal authorities, reform work, practical citizen education, or the broader Systems of Trust framework.

Public KnowledgeThe Awake CitizenCitizen's Academy