Skip to content

Security: jagathsrujan/product-teardown-knowledge-engine

Security

SECURITY.md

Security Policy

Scope

The PTKE repository is currently an open architecture specification with no deployed services or executable code. This security policy will become increasingly relevant as prototype implementations are developed.

Reporting a Vulnerability

If you discover a security vulnerability in any PTKE specification, design, or (future) code:

  1. Do NOT open a public GitHub Issue. This risks premature disclosure.
  2. Email the maintainer directly with the subject line [PTKE SECURITY] <brief description>.
  3. Include:
    • A description of the vulnerability
    • Steps to reproduce (if applicable to a prototype implementation)
    • Potential impact
    • Any suggested mitigations

You will receive an acknowledgment within 72 hours and a detailed response within 7 days.

Security Design Principles

The PTKE architecture incorporates the following security considerations:

Data Sovereignty

  • All data processed and stored exclusively on India-sovereign cloud infrastructure (Yotta/E2E Networks)
  • No cross-border data routing for proprietary manufacturing IP or government workloads
  • Compliant with DPDP Act 2023 requirements

IP & Copyright Compliance

  • Transient processing clean-room architecture: raw media retained ephemerally (30-day window) then discarded
  • Only non-copyrightable factual data (dimensions, temperatures, material grades) persists in the EKG
  • Strict logged-out scraping policy (no credential-based access)
  • DMCA compliance pipeline for applicable jurisdictions

Safety-Critical Output Validation

  • All generative engineering outputs pass through the TAPS + Physics Constraint Engine before user presentation
  • Safety classifier trained on MSDS sheets blocks suggestions violating UL/IEC safety standards
  • Physically impossible outputs (e.g., structurally insufficient wall thickness for load-bearing applications) are hard-blocked

Graph Data Integrity

  • STEP file validation layer checks for non-manifold geometry and open shells before EKG commit
  • Uncertainty quantification on graph edges; low-confidence causal links trigger explicit uncertainty disclosure
  • Numerical properties (torque specs, CTE values, failure thresholds) retrieved from graph DB via tool_use, not generated from parametric memory

Known Limitations (Design-Level)

  • The system is not designed for safety-critical certification (e.g., IEC 61508, DO-178C). It is an engineering intelligence and decision support tool, not a certified design verification system.
  • Material identification via visual texture proxy (BRDF estimation) carries inherent uncertainty; always validate against physical testing before production use.

Supported Versions

Version Status
v0.x (Concept) Architecture specification only — no deployed services

As implementation progresses, this table will track supported versions with active security support.

There aren't any published security advisories