Chapter 5 — Guard and the Ethics-Checklist Card

Guard was a small badger-tween. She wore a small wooden ethics-checklist card pinned to her vest. A small leather ledger, labeled DECISIONS, hung at her hip.

She was short and thick-set. Her fur was a mix of gray and cream, banded in chunky, rounded markings. Guard had steady eyes and an unhurried way of moving. The ethics-checklist card was made of smooth wood. It was about the size of a postcard. Four words were burned into its surface in neat block letters: BIAS. PRIVACY. HARM. CONSENT. The small leather-bound ledger, the DECISIONS ledger, was where she carefully wrote down every ethical question she met. She also recorded the choice she made.

This wasn’t just a habit for Guard. It was her whole job. Guard was present in every kit from Kit 6 onward. She wasn’t a separate ethics-kit. Instead, she was a checking-presence, a quiet shadow, at every step of every other character’s work.

When Catch was out collecting data, Guard would be there, watching. “Is this collection biased?” she might ask. “Whose privacy is at stake here? What harms could come from this? Was consent obtained?”

When Tidy was cleaning up a dataset, Guard would check her work. “Are these cleaning choices removing important voices from the data?” she’d wonder. “Are they making the dataset less representative of the real world?”

When Graph was busy making charts and visuals, Guard would lean in. “Does this chart tell a misleading story?” she’d ask. “Does it make some groups stand out, or does it hide others?”

And when Tell was interpreting what all the data meant, Guard was still there, checking. “Who benefits from this interpretation?” she’d ask. “Who might be harmed by it? And who decided what the data truly means?”

It was critical: Guard never saw ethics as an extra task. It wasn’t a separate concern from the “real data work.” She was always clear about this. “Data ethics is NOT a separate kit,” she would say, her voice firm. “It is part of every step, from Kit 6 onward. Every single step in the data pipeline has ethical stakes.”

The four checks—bias, privacy, harm, consent—were not optional. They weren’t something you did later. They weren’t just for advanced learners. “They are the work,” Guard insisted.

This mattered a great deal. Many people thought of data ethics as an afterthought. They’d say, “First we’ll do the analysis, then we’ll think about ethics.” But Guard knew this approach always failed. By the time the analysis was finished, the choices were already set in stone. Bias might have been built in. Privacy might have been broken or protected. Harms might have been spread around. Consent might have been honored or ignored.

Ethics had to be there from the very beginning. It had to be present all the way through the middle. And it had to be there at the end. Otherwise, it wasn’t truly present at all. Guard’s design, her structural presence from Kit 6 onward, was a promise to that principle.

(Cross-app coordination: Guard’s role mirrors AIForge Wave 13’s ethics cast member. DataForge Guard and AIForge Stake (AI ethics) coordinate. When DataForge data is used to train an AI system, Guard checks at the data side AND Stake checks at the AI side. Mandatory coordination per apps.generated.ts dnCast.intro.)

Guard had grown up in a small village. Her family had been the village’s hearth-keepers for generations. They were the badgers who kept the communal hearth burning. This hearth gave warmth and cooking-heat to families who couldn’t afford their own fires. The work demanded constant attention to fairness. Guard had to decide who received firewood and when. She tracked whose turn it was to cook a meal. She also knew who needed extra warmth on a particularly cold night.

By the age of six, Guard had learned a deep truth. Fair distribution needed constant, structural attention. It wasn’t a once-a-year “let’s-think-about-fairness” meeting. It required daily, embedded attention at every single step. This lesson stayed with her.

She walked to the DataForge academy when she was twenty-two. Datum, the head of the academy, asked her a simple question. “What is data ethics?”

Guard didn’t hesitate. “It is bias, privacy, harm, and consent,” she said. “Embedded in every step. Who benefits? Who’s harmed? Who decided? Ethics is not a separate kit. It is structurally present at every step, from collecting data to interpreting it. The four checks are the work itself, not an after-thought.”

Datum nodded slowly. “You are appointed,” he said.

In her workshop, Guard began every first-day lesson the same way. She unpinned her ethics-checklist card from her vest. She held it up for everyone to see. The words BIAS. PRIVACY. HARM. CONSENT. shone under the lights. Then she opened her DECISIONS ledger.

“I am Guard,” she announced. “The data-pipeline primitive I teach is data ethics. These are the four checks. This is the structural presence. From Kit 6 onward, I am with every other character, at every step. Who benefits? Who’s harmed? Who decided?”

She taught the data-ethics scaffolds, the framework for thinking ethically:

• BIAS: “Whose perspectives shape this dataset?” Guard would ask. She explained that choices made by data collectors, cleaners, or visualizers could all build in a bias. “Our job is to make that bias visible,” she said. “Like if you only ask people in one neighborhood about their favorite food, you’ll get a biased view of the whole city.”
• PRIVACY: “Whose information is in this dataset?” Guard emphasized this point. “Are individuals identifiable?” she’d ask. “Could someone figure out who they are by combining different pieces of information? We need to find the right level of grouping data to protect them. Think about sharing a list of everyone’s exact home address versus just sharing which street they live on.”
• HARM: “What harms could this data cause?” This was a serious question for Guard. She talked about direct harms to individuals in the dataset. She also mentioned indirect harms to communities the dataset was about. “And what about downstream harms?” she’d add. “What happens when someone uses our analysis to make big decisions? Could it unfairly target certain groups?”
• CONSENT: “Did the people in this dataset agree to be in it?” Guard explained the different kinds of agreement. “Was it informed consent, where they knew exactly how their data would be used? Was it implicit consent, like when you agree to terms and conditions? Or was there no consent at all? If there’s no consent, we must ask: is this use justified by a stronger ethical principle?”
• Document every ethical decision in the DECISIONS ledger. Guard always had her ledger open. “Just like Tidy keeps a cleaning log,” she’d say, “we keep a log for ethics. Every question, every choice, every reason.”
• Ethics-by-design, not ethics-by-review. “We don’t just check for ethics at the end,” Guard explained. “That’s like building a bridge and only then checking if it’s safe. The check happens at the beginning, all the way through, and at the end. It’s built into the plan.”
• Cross-app coordination with AIForge Stake. Guard made sure everyone understood that when data moved into AI systems, the ethics check continued. “It’s a hand-off,” she’d say, “from me to Stake, making sure the ethical chain isn’t broken.”
• Refuse projects when ethics requires. “Sometimes,” Guard stated, her voice calm but firm, “the right answer is don’t do this analysis. It’s not a failure. It’s ethics doing its job.” She supported refusal as a valid ethical choice.

She was explicit about this. “I sometimes face a project where the ethical concerns are serious enough that I recommend not proceeding,” Guard said. “Or proceeding only with major changes. That’s not failure. That’s ethics doing its job. The DECISIONS ledger records refusals too. A refusal is part of the data-pipeline’s integrity.”

When students asked Guard whether data ethics was hard, Guard always gave the same answer.

“It is hard,” she’d say. “It is structural, not occasional. The four checks at every step. Bias. Privacy. Harm. Consent. Who benefits? Who’s harmed? Who decided?”

She would then pin the ethics-checklist card back onto her vest. The small leather DECISIONS ledger waited patiently at her hip, ready to record the next choice.

---