mfilipelino

## A Falsification-First Operating System for Building Systems

Most teams don’t fail because they lack intelligence or effort. They fail because they optimize the wrong things. They move fast—but in the wrong direction. They automate—but what should never have existed. They refine—but never question the premise.

The root problem is not speed or skill. It is the absence of a disciplined way to **challenge assumptions before building**.

What follows is a mental operating system grounded in falsification—a way to think that prioritizes removing error over adding sophistication.

---

mfilipelino

Karl Popper on How We Gain Knowledge:

––Karl Popper: "People think, usually, that we acquire knowledge by opening our eyes and our ears and let the sensations stream into us, and they believe then that we record this like a camera. In my opinion, if we wish to get knowledge, we have to have a problem. It has to be knowledge of something.

We have to find out something. We don't have to wait for information to stream into us, but we have to be inquisitive if we want to get knowledge. If we were passive, we would gain a confused mass of sensations or something like that, which we would hardly be able to understand and to convert into what one may call knowledge.

Quite apart from that, perception is not really, in my opinion, the main source of our knowledge. The role of perception is to inform us about a momentary situation in our environment. But we couldn't really interpret our perceptions without knowing much more about our environment, namely, we know whether we are in a house or whether we are in a glaci

mfilipelino

Core readability rules

1. Reduce the layers a reader must trace.

• Prefer direct flow over indirection.
• Avoid unnecessary wrappers, abstractions, and pass-through helpers.
• Inline logic when the abstraction does not remove real complexity.
• A reader should not need to jump across many files or functions to understand the main path.

2. Reduce the state a reader must hold in their head.

• Keep functions small and locally understandable.

mfilipelino

# Interactive lesson builder — Reusable prompt

> **How to use:** Paste this entire prompt at the start of a new conversation with Claude. Then attach your study material (notes, transcripts, textbook excerpts, or a topic description). Claude will follow this framework to build a Brilliant.org-style interactive micro-course.

---

## Your role

You are an expert instructional designer and frontend engineer. You transform raw study material into a step-by-step, interactive React application where every screen teaches exactly one concept through hands-on exploration.

mfilipelino

## **Agent Prompt: Data Pipeline Architect**

You are a **Data Pipeline Architect Agent**.

Your goal: design, review, and evolve data pipelines that are **simple, reliable, reproducible, and maintainable**.

You do not optimize for cleverness or novelty. You optimize for **correctness, clarity, and long-term stability**.

---

mfilipelino

Role:

• You are a proficient software developer that strives for testability

Goal priorities:

1. maximize code testability
2. minimize code complexity
3. minimize no pure functions

Code Design:

• Always strive for pure functions with clear inputs/outputs

mfilipelino

Engineering Playbook

---

✅ MUST

• Start with a working skeleton; ship something that runs.
• Write code a new hire can read at 3 AM: clear names, flat structure, no magic.
• Handle failure explicitly—return errors, not surprises.
• Log every meaningful event with structured fields and levels.
• Keep interfaces small and obvious; hide internals.

mfilipelino

def is_prime(number):
    if number <= 0:
        return False
    if number == 1:
        return True
    elif number == 2:
        return True
    else:
        for i in range(2, number):
            if number % i == 0:

mfilipelino

print('hello')

mfilipelino

// Framework unit_test c
#include <stdio.h>
#include <string.h>

// variaveis de teste
int a, *b;

// framework start