HunterPiggy

What the company appears to be: HunterPiggy is a self-reported explainable signal-to-trajectory engine designed to detect scams, manipulation, and structural anomalies without issuing verdicts. It combines signal detection with institutional mechanism analysis using a framework called PIC–Boson, and models possible trajectories over time.

What changed: During OpenAI Build Week (July 13–21, 2026), the author transformed an existing research component into a standalone, runnable project. Key changes included integrating a trajectory engine, repairing prototype issues, adding bounded simulations, building a PIC adapter, and creating a neutral demonstration.

Single most important open question: Is there evidence of traction or commercial interest in this system beyond its self-reported development?

The description states that HunterPiggy is an explainable signal-to-trajectory engine. It has two main layers:

1. ThreatSignalRouter, which detects transparent markers such as:
   • manipulative or scam-style language;
   • shortened and verification-style URLs;
   • obfuscated contact details;
   • urgency formatting;
   • encoded or high-entropy structures;
   • sensitive contexts;
   • structural anomalies;
   • correlations across multiple signal categories.

1. PICBosonAdapter, which maps detected signals to Ian Tasker’s Political–Institutional Contingency (PIC) framework:
   • PIC–S: Structural Design;
   • PIC–C: Cultural Norms;
   • PIC–P: Procedural Action;
   • PIC–F: Fiscal Prioritisation;
   • PIC–J: Jurisdictional Boundary-Setting;
   • PIC–T: Temporal Constraint.

1. CairoResonanceTrajectoryEngine, which models possible growth and shadow trajectories based on signals, mechanisms, and time.

The system is described as not issuing verdicts but reconstructing how multiple mechanisms may interact over time to produce outcomes.

Inference: The product appears to be a research-oriented tool for analyzing sequences of events or behaviors without classification or automated decision-making.

The author claims that HunterPiggy:

• “Detect the signal. Reconstruct the mechanism. Do not issue a verdict.”
• Focuses on explainable AI rather than simple classification.
• Combines scam detection with institutional analysis, treating both as sequence-reconstruction problems.
• Operates under the principle that individual markers are weak evidence; meaning emerges from correlation, context, mechanisms, and time.

It positions itself as a tool for investigation, not judgment. It is described as:

• Useful for examining institutional and administrative sequences without classifying people or making accusations.
• Designed to avoid automated consequential decisions.

Inference: The positioning reflects an intent to build a responsible, non-judgmental detection system focused on explanation and hypothesis generation rather than automation of outcomes.

The description does not clearly identify target customers or ideal customer profiles (ICP). It mentions:

• Use cases involving scam detection and institutional mechanism analysis.
• A focus on child-safety risks, algorithmic influence, and institutional processes.
• Potential integration with educational tools like KidsPiggy.

However, it does not name specific users, industries, or roles.

Inference: The target audience likely includes researchers, compliance officers, cybersecurity analysts, or educators working in areas involving fraud detection or institutional behavior analysis. But no explicit ICP is stated.

There is no evidence of a business model or pricing structure in the description.

The project is described as:

• A research tool built during a hackathon.
• Not yet independently installable before Build Week.
• Currently analyzing text submitted to it.
• Using transparent baselines rather than trained classifiers.
• Requiring human review.

Inference: No commercialization strategy or pricing model has been reported. The project is presented as an experimental tool with no indication of monetization plans.

The author states that:

• HunterPiggy was built using Codex and GPT-5.6, with human-led decisions.
• It includes:
  • Automated test suite;
  • Deterministic simulations;
  • Reproducible results;
  • Documentation of provenance, attribution, limitations, and division between prior and new work.
• The system integrates:
  • Signal routers;
  • PIC adapter;
  • Trajectory engine;
  • Public pipeline.

It also mentions:

• Repairing invalid data structures;
• Changing simulation output from final-state values to evolving time steps;
• Adding bounded, seeded simulation for reproducibility.

Inference: Technical delivery shows a functional prototype with some automation and structure, but it remains experimental and not yet production-ready.

There is no evidence of traction or maturity beyond the author’s own development efforts:

• The project was part of a hackathon.
• It was previously embedded in a larger research system (Python Zero / Kai256).
• No revenue, customers, or adoption data are provided.
• The system currently analyzes text submitted to it and requires human review.
• False positives and negatives are expected.

Inference: The project is at an early stage of development and lacks any measurable traction or market validation.

The description does not mention competitors or provide a competitive landscape. It focuses on:

• The novelty of combining scam detection with institutional analysis.
• Use of the PIC framework.
• Emphasis on explainability and non-judgmental output.

Inference: No clear competitive positioning is evident. The author does not reference existing tools in this space, nor does it describe how HunterPiggy differs from them.

Key risks and red flags include:

• Lack of commercial traction or revenue data — the system is described only as a research prototype.
• No clear business model or pricing strategy — no indication of monetization plans.
• Self-reported nature of all claims — no independent verification.
• Limited scope: currently analyzes only text submitted to it; requires human review.
• Unproven scalability or performance — described as using transparent baselines, not trained classifiers.
• No evidence of product-market fit — no mention of user feedback or demand.

Inference: Without external validation or usage data, the project remains speculative and unproven in terms of viability or impact.

1. What specific institutional or regulatory use cases are you targeting?
2. How do you plan to validate the accuracy of trajectory reconstructions?
3. Are there any existing partnerships or pilot programs with organizations using this system?
4. What is your roadmap for transitioning from prototype to a deployable product?
5. How will you handle privacy and data governance in real-world deployments?
6. What are the key assumptions behind the PIC framework application here?
7. Have you considered integrating feedback loops or adaptive learning into the system?