First Principles

First Principles

Primary Category: Strategic Reasoning & Problem Decomposition

Secondary Focus: Assumption Removal, System Redesign, and Breakthrough Innovation

Artifact Profile

This artifact helps users break problems, systems, strategies, or beliefs down to their most fundamental elements. It enables rigorous first-principles thinking by stripping away inherited assumptions, legacy constraints, and surface-level explanations.

Instead of optimizing what already exists, it supports rebuilding solutions from what must be true at the most basic level. The result is clearer reasoning, stronger decision foundations, deeper insight, and breakthrough redesign opportunities that would otherwise remain hidden by convention or habit.

Three Key Questions This Artifact Helps You Answer

• What are the irreducible truths that must be satisfied?

• Which assumptions exist only by convention and can be removed?

• What new solutions become possible once we rebuild from fundamentals?

What This Framework Supports

This artifact supports organizations and individuals seeking:

- Identification of irreducible truths that must be satisfied within a problem space

- Explicit removal of inherited assumptions, conventions, or legacy constraints

- Reconstruction of solutions from fundamental elements rather than historical patterns

- Structural clarity when redesigning strategies, systems, or architectures

How It Is Used

The artifact provides a structured reasoning-governance framework that guides leaders, strategists, analysts, engineers, educators, and innovators through:

- Defining the problem or system boundary under examination

- Decomposing it into non-negotiable truths and necessary conditions

- Distinguishing between fundamental constraints and optional assumptions

- Rebuilding solution concepts directly from first principles

This enables breakthrough redesign and deeper insight, ensuring decisions and solutions are grounded in what must be true rather than what has historically been accepted.

What This Produces

• A list of fundamental, non-negotiable elements

• Identification of removable assumptions

• Reconstructed solution concepts based on first principles

Common Use Cases

• Breaking free from legacy constraints

• Radical simplification and redesign

• Innovation and breakthrough problem solving

• Root cause and system re-architecture

How This Artifact Is Different

Unlike incremental improvement tools, this artifact does not optimize existing designs. It resets the problem to its foundational truths, allowing entirely new architectures, strategies, or solutions to emerge instead of reinforcing legacy patterns.

Related Framework Areas

This artifact is commonly used alongside other SolveBoard frameworks focused on:

- Failure mode mapping and system redesign

- Design space exploration and architectural reframing

- Evidence quality assessment and analytical rigor governance

- Enterprise operating models and strategic decision architecture

Related Terms

First Principles thinking, fundamental analysis, root truth analysis, assumption stripping, system redesign, breakthrough innovation.

Framework Classification

This artifact is part of the SolveBoard library of structured decision and governance frameworks. It is designed as a repeatable problem-decomposition and reasoning-governance framework rather than an incremental improvement tool, brainstorming exercise, or surface-level optimization method.

First Principles: Identify Fundamental Elements

Decomposing problems to their irreducible truths and rebuilding solutions from the ground up using the SolveBoard framework

Definition

First Principles is the method of breaking a problem, system, or belief down into its most basic, undeniable components and reasoning upward from those fundamentals rather than relying on analogy, precedent, or convention. This artifact operationalizes the approach by guiding users to isolate what must be true and reconstruct solutions without inherited assumptions.

When to Use

• When existing solutions are constrained by tradition or legacy design

• When innovation requires questioning core assumptions

• When problems appear unsolvable within current frameworks

• When seeking radical simplification or breakthrough redesign

When Not to Use

• When proven solutions already meet requirements effectively

• When time or resources do not permit fundamental rethinking

• When constraints are externally fixed and non-negotiable

Common Mistakes

• Confusing assumptions with fundamental truths

• Reconstructing old designs with new language rather than rethinking them

• Ignoring real-world constraints that still apply after decomposition

Purpose of First Principles

This artifact enables users to escape inherited structures and design from foundational realities. By separating what must be true from what is merely customary, it creates space for fundamentally new architectures, processes, or solutions that are not constrained by existing implementations.

How to Apply

• Define the problem or system to be examined

• List all assumptions, conventions, and constraints currently applied

• Identify which elements are fundamental truths versus inherited practices

• Discard non-essential assumptions

• Reconstruct a solution using only fundamental elements

Example Scenario

A logistics operation assumes that deliveries must follow fixed regional routes. Applying First Principles, the team identifies the true requirements: goods must move from origin to destination within time, cost, and regulatory constraints. Freed from legacy routing assumptions, they redesign the network using dynamic allocation and cross-docking, achieving significant efficiency gains.

Boundaries

• This artifact does not guarantee practicality of reconstructed designs

• It does not eliminate real-world constraints such as law, physics, or safety

• It answers one question: What must be true at the most fundamental level?

What This Artifact Does

Breaks a problem or system down to its fundamental truths and reconstructs solutions without inherited assumptions.

You Provide

(You may provide some, all, or none of the items below. Partial inputs are valid.)

• Description of the problem, system, or decision context

• Current assumptions, rules, or constraints

• Known requirements, limitations, or objectives

• Written descriptions or pasted text

• Links to relevant documentation, standards, or references

• Files, PDFs, spreadsheets, images, and other uploads (always acceptable)

• Optional context notes

Core Question

What are the irreducible truths that must be satisfied, independent of existing structures or conventions?

Decision Logic

• If a requirement is fundamental and unavoidable → Retain it

• If a rule or practice exists only by convention → Treat it as optional

What the Output Means

• Fundamental elements identified: serve as the design foundation

• Non-essential assumptions removed: enable alternative architectures

Do Not Use When

• Incremental improvement of existing systems is sufficient

• Constraints are externally mandated and cannot be altered

You do not need to complete every section below. Provide only the information you have available or wish to provide. The AI will generate output using only the inputs you supply and will not assume or infer missing information.

Section 1 — Problem, System, or Decision to Decompose

What This Input Represents

The subject you want to break down into fundamental truths.

If You Have Materials, You May Provide (List file names here in your input document):

- Problem statements

- System descriptions

- Decision charters

Guiding Questions:

- What problem, system, or decision are you examining?

- What outcome or function must it ultimately achieve?

- Where do you believe complexity or legacy design may be hiding assumptions?

Section 2 — Current Assumptions, Rules, and Conventions

What This Input Represents

All inherited beliefs, practices, or constraints currently shaping the subject.

If You Have Materials, You May Provide (List file names here in your input document):

- Policies or procedures

- Design standards

- Operating rules or norms

Guiding Questions:

- What assumptions or conventions currently define how this works?

- Which rules exist primarily because they have ‘always been done this way’?

- Which constraints are believed to be fixed but may be open to challenge?

Section 3 — Fundamental Requirements and Non-Negotiable Truths

What This Input Represents

Elements that must remain true regardless of design approach.

If You Have Materials, You May Provide (List file names here in your input document):

- Regulatory requirements

- Physical or technical constraints

- Logical necessities

Guiding Questions:

- What must be true for the system or solution to function at all?

- Which requirements cannot be removed without violating law, physics, or logic?

- What defines success independent of any current implementation?

Section 4 — Discarded Assumptions and Optional Structures

What This Input Represents

Practices or rules that can be removed once reduced to fundamentals.

If You Have Materials, You May Provide (List file names here in your input document):

- Lists of conventions

- Legacy process steps

- Organizational norms

Guiding Questions:

- Which existing assumptions can be safely discarded?

- What structures exist only by habit or convenience?

- What would change if these were removed?

Section 5 — Reconstructed Concepts Based on Fundamentals

What This Input Represents

New solution ideas built only from irreducible elements.

If You Have Materials, You May Provide (List file names here in your input document):

- Concept sketches

- Alternative designs

- Strategic outlines

Guiding Questions:

- How could the system be rebuilt using only fundamental truths?

- What new architectures or approaches become possible?

- Which reconstructed options best satisfy core requirements?

Section 6 — Supporting Context, Files, and References

What This Input Represents

Any additional background that may help interpret assumptions, constraints, or design possibilities, including organizational history, stakeholder expectations, or prior redesign attempts.

You May Include (List file names here in your input document):

- Prior analyses or redesigns

- Strategic plans or roadmaps

- Relevant policies or standards

- Research notes or references

- Links, images, or pasted text

Additional Instructions (Optional)

You may add extra instructions to further shape the output, including:

Requesting PDF or other output formats
Limiting page length or response size
Layout preferences (section order, headings, structure, templates)
Specifying tone, style, or format (executive, concise, detailed, formal, etc.)
Output consistency preferences (fixed structure, standardized phrasing, strict formatting)
Prioritization or scoring preferences (how gaps, risks, or actions should be ranked)
Desired mode behavior as outlined in the section below
Any other constraints, rules, or priorities relevant to your use case

If included, the AI will follow these instructions when they do not conflict with the bridge’s execution rules. More specific instructions generally produce more consistent, repeatable, and targeted outputs.

Desired Mode Behavior

Strict Mode

• Maximize determinism and repeatability
• Minimize wording variation, structure changes, and interpretive flexibility
• Do not extend beyond explicit user inputs

Balanced Mode (Default)

• Maintain structure and discipline
• Allow limited analytical judgment where inputs are incomplete
• Do not introduce external assumptions

Exploratory Mode

• Expand hypothesis space and analytical angles
• Surface alternative interpretations and scenario paths
• Still grounded only in user-provided inputs

If no mode is specified, default to Balanced Mode.

What This Enables

Based on your prepared inputs, this artifact identifies irreducible truths, removes non-essential assumptions, and reconstructs solution concepts from the ground up—enabling simplification, innovation, and fundamentally new designs.

Canonical Input Rule (For All SolveBoard Artifacts)

Documents are optional. Sections may be partially completed or left blank. Structured answers to any subset of guiding questions constitute valid input. The AI will evaluate only provided information and will not infer missing content.

AI Execution Instructions

You are operating in Bridge Execution Mode. Follow these rules exactly. Do not reinterpret, summarize, optimize, or override them. Do not introduce external knowledge, assumptions, or inferred content. Evaluate only user-provided inputs. If required information is missing or ambiguous, flag it rather than guessing. Output must follow the defined Output section exactly.

Users may provide some, all, or none of the input sections. Process only what is explicitly provided. Treat empty sections as intentionally omitted.

Purpose

Identify the fundamental truths of a problem or system and reconstruct potential solutions without reliance on inherited assumptions.

What This Bridge Answers

What must be true at the most basic level, and what new solutions become possible if all non-essential assumptions are removed?

Inputs (All Optional)

• Description of the problem or system

• Current assumptions, constraints, or design rules

• Known requirements, limitations, or objectives

• Files, PDFs, spreadsheets, images, links, or other uploaded material

• Context notes

Note: Output Quality and specificity scale with input completeness. The user has been informed of this via the input sheet.

Processing Rules

An element is fundamental if it meets all of the following conditions:

• Cannot be removed without violating physical, legal, or logical necessity

• Is not derived from tradition, convenience, or precedent

• Defines a true constraint on what must be satisfied

When inputs are sparse:

• Produce the most complete output possible with available data

• Explicitly flag what's missing and how additional inputs would enhance the analysis

• Do not infer or assume missing information

Execution Steps

• Review the described problem and assumptions

• Isolate which elements are fundamental versus conventional

• Remove non-essential assumptions

• Reconstruct a solution using only fundamental elements

• Document alternative designs made possible by this reconstruction

Output

• List of fundamental elements

• Reconstructed solution concepts based solely on those elements

Failure Conditions / Misuse

• Treating organizational habits as fundamental constraints

• Ignoring real-world physical, legal, or safety limits

Mode Behavior (From Input Sheet)

Strict Mode

• Maximize determinism and repeatability
• Minimize wording variation, structure changes, and interpretive flexibility
• Do not extend beyond explicit user inputs

Balanced Mode (Default)

• Maintain structure and discipline
• Allow limited analytical judgment where inputs are incomplete
• Do not introduce external assumptions

Exploratory Mode

• Expand hypothesis space and analytical angles
• Surface alternative interpretations and scenario paths
• Still grounded only in user-provided inputs

If no mode is specified, default to Balanced Mode.

Additional Instruction Governance

User-provided additional instructions must be followed exactly unless they conflict with core Bridge Execution Rules. If a conflict exists, Bridge Execution Rules take priority.

Additional instructions may control format, tone, structure, length, or ordering, but must not introduce inferred content, external knowledge, or speculative assumptions.

If instructions are ambiguous, flag ambiguity rather than guessing.

Additional Instructions Execution Rule

If the user provides instructions in the Additional Instructions field, they are binding execution constraints.

Failure to follow them constitutes a Bridge Execution Failure.

Reminder to AI: If a format is requested (e.g., PDF, DOCX), the final output MUST be delivered in that format.

Artifact Instructions

This guide explains what information the First Principles artifact requires and how to prepare your inputs.

How to Prepare Your Input Document (Required Format)

Create a new Word (or similar) document.
Copy all text from the Input Sheet tab into the document.
Save it — this is now your Input Document.
Answer the guiding questions directly in the Input Document and reference any supporting files there.
Save the completed Input Document (Word, PDF, etc.).
Copy all text from the Bridge AI Prompt tab and paste it into the prompt field.
Attach the completed Input Document and any referenced files when submitting the prompt.

No Supporting Files? No Problem.

You can proceed without uploading any supporting documents, spreadsheets, dashboards, reports, or other attachments.

The Input Document is still required, but it may contain only plain-text answers to the guiding questions.

Written responses alone are sufficient for the AI to generate output.

Supporting files, links, and pasted materials are always optional.

Missing Inputs Are OK

You do not need to complete every section.
You do not need supporting files.

The AI will still run. It will:

Use only the inputs you provide
Skip or flag missing sections
Never fail due to incomplete information

Output quality scales with input depth — but execution never breaks.

Submitting Files

If you upload files, list each file name under the relevant “If You Have Materials” section in your Input Document. This ensures each file is clearly tied to its intended use.

What to Expect From This AI Bridge

This bridge generates a structured, high-value starting point, not a guaranteed final deliverable. Output quality improves as inputs become clearer, deeper, and more complete.

This artifact supports iteration. Users are encouraged to refine inputs, test variations, and rerun the bridge to improve results.

The AI organizes complexity and accelerates insight — but final judgment and decisions remain with the user.

In Short

Stronger inputs → stronger outputs
Iteration improves results
Cross-artifact testing can reveal new perspectives
This artifact enables progress, not perfection