Skip to content

Feature Development Protocol

Feature Development Protocol

Parallel Process Framework for HeliosDB Feature Development

Document Version: 1.0 Date: October 26, 2025 Status: Mandatory for all new features


Overview

Every new feature developed for HeliosDB MUST follow this parallel process framework to ensure:

  1. IP Protection: Patents filed before disclosure
  2. Investor Confidence: Series A materials stay current
  3. Competitive Advantage: Defensive publications block competitors
  4. Strategic Planning: Trade secret vs. publication decisions

Protocol Sections

This protocol has been split into manageable sections for easier navigation and reference:

Mandatory Parallel Processes

When developing ANY new feature, you MUST execute these 5 processes in parallel:

  1. Process 1: Series A Materials Update

    • Trigger: Feature design complete (before implementation)
    • Timeline: Within 2 days of feature completion
    • Owner: Product Manager + Marketing
    • Updates ONE_PAGER, ELEVATOR_PITCH, PITCH_DECK, and VALUATION documents
  2. Process 2: Patent Detection & Portfolio Update

    • Trigger: Feature design complete (architectural phase)
    • Timeline: Within 5 days of feature architecture approval
    • Owner: Legal + Engineering Lead
    • Patent detection, confidence scoring, and portfolio updates
  3. Process 3: Invention Disclosure Preparation

    • Trigger: Patent confidence ≥70% detected
    • Timeline: Within 10 days of patent detection
    • Owner: Engineering Lead + Legal
    • Formal invention disclosure documentation for patent attorney
  4. Process 4: Defensive Publication

    • Trigger: Patent confidence 50-69% OR strategic decision to publish
    • Timeline: Within 15 days of patent decision
    • Owner: Legal + Engineering
    • Create prior art to block competitor patents
  5. Process 5: Trade Secret vs. Publication Decision

    • Trigger: Patent confidence <70% OR strategic IP decision required
    • Timeline: Within 7 days of patent analysis
    • Owner: Legal + CTO + CEO
    • Decide whether to publish or keep as trade secret
  6. Process 6: Documentation Update & Link Validation

    • Trigger: Feature implementation complete (code merged)
    • Timeline: Within 2 days of feature completion
    • Owner: Engineering Lead + Technical Writer
    • Update documentation, validate links, create release reports

Enforcement and Compliance

  • Enforcement and Compliance

    • Pre-merge checklist (required for PR approval)
    • Automated checks (CI/CD pipeline)
    • Quarterly IP review process
    • Decision tree and quick reference
    • Contact information and escalation
  • Compliance Tracking & Audit History

    • Latest audit results (November 1, 2025)
    • Compliance summary by feature
    • Critical gaps identified
    • Action items and remediation plans
    • Compliance metrics dashboard

Quick Reference: Decision Tree

New Feature Developed
Patent Detection (2 days)
┌───────────────────────────────┐
│ Confidence Score? │
└───────────────────────────────┘
↓ ↓ ↓
≥70% 50-69% <50%
↓ ↓ ↓
File Patent Defensive Trade Secret?
(10 days) Publication ↓
↓ (15 days) Yes: Protect
Invention ↓ No: Skip
Disclosure Publish to ↓
↓ IP.com/arXiv Document
Patent ↓ Decision
Attorney Update ↓
↓ Portfolio Update
File with ↓ Register
USPTO Prior Art ↓
↓ Created [END]
Update ↓
Portfolio [END]
[END]
┌──────────────────────────────────────────────┐
│ PARALLEL: Update Series A (2 days) │
│ PARALLEL: Create Release Report (2 days) │
└──────────────────────────────────────────────┘

Key Timelines

ProcessTimelineTrigger
Series A Materials2 daysFeature design complete
Patent Detection5 daysArchitecture approved
Invention Disclosure10 daysPatent confidence ≥70%
Defensive Publication15 daysPatent confidence 50-69%
Trade Secret Decision7 daysPatent confidence <70%
Documentation Update2 daysCode merged

Contact and Escalation

IP Questions: legal@heliosdb.com Patent Attorney: [Name], [Firm], [Email] Trade Secret Custodian: CTO Series A Materials Owner: VP Product / Marketing


Document Version Control

File: docs/guides/developer/FEATURE_DEVELOPMENT_PROTOCOL.md Version: 1.0 Last Updated: October 26, 2025 Next Review: January 1, 2026 Owner: CTO + Legal


Important Notes

This protocol is MANDATORY for all HeliosDB feature development.

Non-compliance may result in:

  • IP loss and patent opportunities missed
  • Investor confidence erosion
  • Competitive disadvantage
  • Legal risks

Exemplar Feature: heliosdb-pqc achieved 100% compliance - use as template


Documentation Files

All sections of this protocol are located in:

docs/guides/developer/
├── FEATURE_DEVELOPMENT_PROTOCOL.md (this index)
├── FEATURE_DEVELOPMENT_PROTOCOL_PROCESS_1_SERIES_A.md
├── FEATURE_DEVELOPMENT_PROTOCOL_PROCESS_2_PATENT_DETECTION.md
├── FEATURE_DEVELOPMENT_PROTOCOL_PROCESS_3_INVENTION_DISCLOSURE.md
├── FEATURE_DEVELOPMENT_PROTOCOL_PROCESS_4_DEFENSIVE_PUBLICATION.md
├── FEATURE_DEVELOPMENT_PROTOCOL_PROCESS_5_TRADE_SECRET.md
├── FEATURE_DEVELOPMENT_PROTOCOL_PROCESS_6_DOCUMENTATION.md
├── FEATURE_DEVELOPMENT_PROTOCOL_ENFORCEMENT.md
└── FEATURE_DEVELOPMENT_PROTOCOL_COMPLIANCE_TRACKING.md

Start here: Process 1: Series A Materials Update →