Research

Research documents describe how PunchCard Labs frames technical findings before they become public reports or advisories. The emphasis is on reproducible reasoning, conservative claims, and clear separation between observed behavior and inferred impact.

A public research artifact should make its assumptions visible. It should describe what was tested, what was not tested, what evidence supports the claim, and what uncertainty remains. That discipline matters more than aggressive wording: senior readers can infer quality from precision, restraint, and the absence of unsupported severity inflation.

MethodologyResearch workflow, evidence standards, and validation expectations.Severity ModelHow technical impact, exposure, exploitability, and coordination context are weighed.

Research Standard

Research pages should avoid exploit tutorials unless a controlled publication decision explicitly requires technical detail. Public language should enable remediation and risk understanding without creating unnecessary operational advantage for abuse.

Research documentation should explain method and evidence boundaries without creating operational instructions for abuse. The goal is reproducible judgment, not public weaponization.

Page Standard

This page is part of the public operational surface. It should route readers to the correct action, state the relevant boundary, and avoid claims that are not backed by a document, tool, schema, or release record.

Program Structure

The research section now includes a program map that separates research lines from publication outputs. That page is the bridge between methodology, severity analysis, advisories, reports, data, and tools. It helps decide whether a future artifact should become an advisory, a report, a schema, an example, or a local utility.

Research Program MapResearch lines, outputs, and publication boundaries.MethodologyHow research claims are bounded and reviewed.Severity ModelHow impact, exploitability, and context are assessed.