What is the Symbol Word Protocol?
The Symbol Word Protocol (SWP) is a structured tagging system designed to make documents more understandable to AI systems. By adding semantic tags to your content, you help Large Language Models (LLMs) like ChatGPT, Claude, and other AI assistants process your documents with greater accuracy, consistency, and context awareness.
Why SWP Matters
AI systems work best when they understand the structure and intent of content. SWP provides:
- Explicit Structure: Tags tell AI exactly what each section represents
- Reduced Ambiguity: Clear metadata prevents misinterpretation
- Consistent Processing: Same document structure yields consistent AI responses
- Domain Context: Industry-specific tags add regulatory and compliance awareness
Core SWP Tags
These tags are applied to every document, regardless of which framework you choose:
@phase:
Development stage indicating where a document is in its lifecycle
@weight:
Complexity score (1-10) based on content depth and technical detail
@symbolic_id:
Unique identifier for cross-referencing and traceability
@swp_sum:
Cryptographic checksum for content integrity verification
@priority:
Urgency level: Critical, High, Medium, Low
@category:
Content type: Strategic, Operational, Technical, Creative
@phase: 3.2 - Design - Technical Specs
@weight: 7
@symbolic_id: 12
@swp_sum: 48291
@priority: High
@category: Technical
@status: In Progress
@project_type: Enterprise
Free vs Pro Features
| Feature |
Free Tier FREE |
Pro Plan PRO |
| Single-file SWP tagging |
Unlimited |
Unlimited |
| Core SWP tags |
All tags |
All tags |
| Document proof generation |
Yes |
Yes |
| Batch processing (multi-file) |
- |
180/month |
| Domain frameworks |
- |
All 6 frameworks |
| GPT Idea Builder |
- |
180/month |
| Document Refinement |
- |
180/month |
Tip: The free tier is perfect for individual documents, journaling, and learning the SWP system. Upgrade to Pro when you need batch processing for projects or industry-specific compliance tags.
Using SWP with AI Systems
SWP-tagged documents work seamlessly with AI assistants. Here's how to leverage them:
With ChatGPT / Claude
Example Prompt
"I'm providing an SWP-tagged document. Please read the metadata tags at the top to understand the context, development phase, and priority before responding to my questions."
With AI-Powered IDEs (Cursor, Replit, etc.)
Include SWP-tagged requirements and specifications in your project. The AI will use the phase and priority tags to understand which features to prioritize.
With Note-Taking / Journal Apps
Tag your notes and journal entries to create searchable, structured content. The @category and @status tags help you track progress on ideas over time.
@phase: 1.1 - Ideation - Brainstorm
@category: Creative
@status: Draft
@priority: Medium
General Framework FREE
The General framework applies standard SWP tags suitable for any document type. It's the default framework and is available to all users, including free tier.
Best Use Cases
- Project Documentation: PRDs, specifications, requirements
- Personal Notes: Journals, idea logs, research notes
- Business Documents: Proposals, reports, presentations
- Creative Writing: Story outlines, character notes, world-building
- Technical Documentation: API docs, user guides, tutorials
Extended Optional Tags
Enable "Show Extended Tags" to access additional metadata options:
@project_type:
MVP, Enterprise, Startup, Personal, Research
@use_case:
Specific application context
@target_audience:
Developers, Executives, End Users, etc.
@milestone:
MVP Launch, Beta Release, Alpha Demo
@risk_level:
Low, Moderate, High, Critical
@timeline:
Target completion timeframe
Example: Tagged Project Proposal
@phase: 2.1 - Research - Market Analysis
@weight: 5
@symbolic_id: 8
@swp_sum: 31847
@priority: High
@category: Strategic
@status: In Review
@project_type: Startup
@target_audience: Investors
@milestone: Seed Round
@timeline: Q2 2026
Framework Tags
These 7 compliance tags are automatically applied when using the Healthcare framework:
@sector: Healthcare
Identifies the document as healthcare domain
@regulatory_standards: HIPAA, GDPR
Applicable data protection regulations
@compliance_posture: PHI Protection
Protected Health Information handling requirements
@data_sensitivity: Patient Data, Clinical Records
Data classification for healthcare
@audit_trail: Required
Logging and audit requirements for compliance
@data_minimization: Required
Collect only necessary data principle
@operational_principles: Need-to-Know Access, Encryption at Rest
Security and access control guidelines
Best Use Cases
- Electronic Health Records (EHR): Patient record templates, clinical notes
- Clinical Decision Support: Treatment protocols, diagnostic workflows
- Healthcare Analytics: Population health reports, outcome tracking
- Telehealth Platforms: Virtual visit documentation, remote monitoring
- Medical Device Documentation: Device specs for FDA compliance
Example: Clinical Protocol Document
@phase: 4.2 - Core - Implementation
@weight: 8
@priority: Critical
@category: Operational
@sector: Healthcare
@regulatory_standards: HIPAA, GDPR
@compliance_posture: PHI Protection
@data_sensitivity: Patient Data, Clinical Records
@audit_trail: Required
@data_minimization: Required
@operational_principles: Need-to-Know Access, Encryption at Rest
Compliance Note: These tags signal to AI systems that the document contains sensitive healthcare data. LLMs should apply appropriate caution and not store or transmit PHI inappropriately.
Framework Tags
These 7 safety-focused tags are automatically applied when using the Robotics framework:
@sector: Robotics
Identifies the document as robotics/autonomous domain
@regulatory_standards: ISO 13482, IEC 61508
Safety and functional safety standards
@compliance_posture: Safety-Critical Controls
High-reliability system requirements
@data_sensitivity: Sensor Data, Control Systems
Data classification for autonomous systems
@fail_safe_protocol: Required
Graceful degradation and emergency stop requirements
@real_time_processing: Required
Latency-critical processing constraints
@operational_principles: Redundancy, Human Override, Graceful Degradation
Safety design principles
Best Use Cases
- Autonomous Vehicles: Navigation specs, sensor fusion docs, safety cases
- Industrial Robotics: Manufacturing automation, collaborative robot specs
- Drone Systems: Flight control, obstacle avoidance, geofencing
- Medical Robotics: Surgical robot requirements, safety interlocks
- Warehouse Automation: AGV navigation, pick-and-place systems
Example: Autonomous Navigation Specification
@phase: 3.1 - Design - Architecture
@weight: 9
@priority: Critical
@category: Technical
@sector: Robotics
@regulatory_standards: ISO 13482, IEC 61508
@compliance_posture: Safety-Critical Controls
@data_sensitivity: Sensor Data, Control Systems
@fail_safe_protocol: Required
@real_time_processing: Required
@operational_principles: Redundancy, Human Override, Graceful Degradation
Safety Note: These tags indicate safety-critical documentation. AI systems processing this content should flag any ambiguity in safety requirements and never suggest shortcuts that compromise fail-safe mechanisms.
Framework Tags
These 7 legal compliance tags are automatically applied when using the Legal framework:
@sector: Law
Identifies the document as legal domain
@regulatory_standards: GDPR, CCPA, EULA
Data protection and licensing regulations
@compliance_posture: Privilege-Aware Controls
Attorney-client privilege protection
@data_sensitivity: Legal Documents, Intellectual Property
Data classification for legal content
@document_integrity: Required
Ensures unaltered processing of legal content
@audit_trail: Required
Logging and audit requirements
@operational_principles: Immutable Logs, Non-Repudiation
Legal accountability guidelines
Best Use Cases
- Contract Management: Agreement templates, clause libraries, amendments
- eDiscovery: Document review, privilege logging, production sets
- Compliance Documentation: Policy documents, regulatory filings
- Intellectual Property: Patent applications, trademark filings, IP portfolios
- Legal Research: Case analysis, precedent summaries, legal briefs
Example: Contract Template Document
@phase: 4.1 - Core - Foundation
@weight: 7
@priority: High
@category: Operational
@sector: Law
@regulatory_standards: GDPR, CCPA, EULA
@compliance_posture: Privilege-Aware Controls
@data_sensitivity: Legal Documents, Intellectual Property
@document_integrity: Required
@audit_trail: Required
@operational_principles: Immutable Logs, Non-Repudiation
Privilege Note: Documents tagged with the Legal framework signal potential attorney-client privilege. AI systems should not summarize or disclose content that could waive privilege protections.
Framework Tags
These 7 education compliance tags are automatically applied when using the Education framework:
@sector: Education
Identifies the document as education domain
@regulatory_standards: FERPA, COPPA, GDPR
Student privacy and children's data protection
@compliance_posture: Student Data Protection
Core educational privacy requirement
@data_sensitivity: Student Records, Learning Analytics
Data classification for education
@accessibility: WCAG 2.1 AA Required
Inclusive education accessibility standards
@content_standards: Common Core, NGSS, State Standards
Curriculum alignment frameworks
@operational_principles: Age-Appropriate Design, Parental Consent, Data Minimization
EdTech ethical guidelines
Best Use Cases
- Learning Management Systems (LMS): Course structures, assignment specs, gradebook designs
- Curriculum Mapping: Standards alignment, lesson plans, scope and sequence
- Assessment Platforms: Test specifications, rubrics, adaptive learning algorithms
- Student Information Systems: Enrollment workflows, transcript management
- Educational Analytics: Learning outcome tracking, intervention triggers
Example: LMS Course Specification
@phase: 3.2 - Design - Technical Specs
@weight: 6
@priority: High
@category: Operational
@sector: Education
@regulatory_standards: FERPA, COPPA, GDPR
@compliance_posture: Student Data Protection
@data_sensitivity: Student Records, Learning Analytics
@accessibility: WCAG 2.1 AA Required
@content_standards: Common Core, NGSS, State Standards
@operational_principles: Age-Appropriate Design, Parental Consent, Data Minimization
Privacy Note: Documents tagged with the Education framework indicate student data involvement. AI systems should never store, share, or process student PII beyond the immediate task, and must respect parental consent requirements for users under 13.
Framework Tags
These 7 financial compliance tags are automatically applied when using the Finance framework:
@sector: Financial Services
Identifies the document as financial domain
@regulatory_standards: SOX, GDPR, FINRA, Basel III, PCI-DSS
Financial regulations and compliance frameworks
@compliance_posture: Financial Controls Required
Core financial control requirement
@data_sensitivity: PII, Transaction Data, Account Information
Data classification for financial records
@audit_trail: Required
Mandatory transaction logging for compliance
@risk_classification: Required
Risk categorization for financial instruments
@operational_principles: Data Encryption, Immutable Logs, Non-Repudiation
Financial security best practices
Best Use Cases
- Account Statements: Monthly statements, transaction summaries, balance reports
- Transaction Processing: Payment workflows, transfer validation, settlement systems
- Risk Management: Risk assessments, exposure analysis, hedging strategies
- Regulatory Reporting: SOX compliance docs, FINRA filings, Basel III capital reports
- Portfolio Management: Investment strategies, asset allocation, performance tracking
- Compliance Automation: Policy enforcement, audit preparation, control monitoring
- Treasury Operations: Cash management, liquidity planning, funding strategies
Example: Account Statement
@phase: 2.1 - Blueprint - System Architecture
@weight: 5
@priority: Medium
@category: Financial Reporting
@sector: Financial Services
@regulatory_standards: SOX, GDPR, FINRA, Basel III, PCI-DSS
@compliance_posture: Financial Controls Required
@data_sensitivity: PII, Transaction Data, Account Information
@audit_trail: Required
@risk_classification: Required
@operational_principles: Data Encryption, Immutable Logs, Non-Repudiation
Compliance Note: Documents tagged with the Finance framework indicate financial data handling requirements. AI systems should enforce data encryption, maintain immutable audit logs, and ensure non-repudiation for all transactions. Never process or store unencrypted financial PII.
Production Deployment Guide
This guide covers deploying SWP-tagged applications and integrating IdeaPhase into your production systems.
Frequently Asked Questions
Q: How do I deploy my SWP-tagged documents to production?
Tagged documents can be exported directly from IdeaPhase. Use the download buttons to get your tagged files (.txt format) or proof receipts (.txt format). These files can be integrated into any system that processes text.
Q: Can I verify document proofs after deployment?
Yes! Every proof includes a SHA256 hash and UTC timestamp. To verify: regenerate the hash from your document content using SHA256, then compare it to the stored proof. The hashes should match exactly if the document hasn't been modified.
Q: How do I integrate SWP tags with my AI system?
Add the recommended system prompt (available on the home page) to your LLM configuration. The prompt instructs AI to look for SWP meta-data headers first, then process content based on phase and weight indicators.
Q: What's the best way to batch process documents in production?
Pro subscribers can use the Batch Processing tab to tag multiple documents at once. Each document receives its own proof, and you can download all tagged files plus proofs as a batch. For API integration, contact us about enterprise access.
Q: How do domain frameworks affect my production workflow?
Domain frameworks (Healthcare, Robotics, Legal, Education, Finance) add compliance-specific tags. When your AI system sees @sector: Healthcare and @regulatory_standards: HIPAA, it knows to apply appropriate data handling rules. Choose the framework that matches your production domain.
Q: Are document proofs legally binding?
Cryptographic proofs provide strong evidence of document existence at a specific time. While not a substitute for legal registration, they serve as supporting evidence for IP claims, patent filings, and dispute resolution. Each proof includes a timestamp and can be independently verified.
API Integration (Enterprise)
For high-volume production deployments requiring API access, IdeaPhase offers enterprise integration options:
- REST API: Programmatic access to tagging and proof generation
- Webhook Notifications: Real-time proof confirmation callbacks
- Custom Frameworks: Industry-specific tag schemas for your domain
- SLA Guarantees: Uptime and response time commitments
Contact ideaphase.needs@gmail.com for enterprise inquiries.
Security Considerations
- Data Privacy: Documents are processed but not stored permanently. Only proof hashes are retained.
- HTTPS Only: All traffic is encrypted in transit.
- No Third-Party Sharing: Your content is never shared with external parties.
- Compliance Ready: Framework tags indicate but don't enforce compliance; implement appropriate controls in your systems.
