Methodology, templates, and operational infrastructure for Signal Corps — a boutique data consulting practice helping SMBs build semantic data foundations before deploying AI.
Find a file
2026-08-22 07:02:22 -04:00
.gitignore chore: gitignore .env files and editor backups 2026-08-16 08:23:02 -04:00
README.md Add Ideas & Deferred Concepts v1.0 2026-07-31 19:06:46 -04:00
Signal_Corps_AppLocked_Data_Protocol_v1_0.docx Add App-Locked Data Protocol v1.0 2026-07-31 17:31:24 -04:00
Signal_Corps_Brand_Guide_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Ethical_Framework_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Ideas_v1_0.docx Add IDEA-010 through IDEA-012 (RAG service ideas) 2026-08-22 07:02:03 -04:00
Signal_Corps_Master_Doc_1.0 Update Signal_Corps_Master_Doc_1.0 2026-08-01 21:35:12 +00:00
Signal_Corps_Methodology_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_NoMetadata_DB_Protocol_v1_0.docx Add No-Metadata Database Protocol v1.0 2026-07-31 18:14:19 -04:00
Signal_Corps_Phase1_Methodology_v2.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Pre-Launch_Checklist_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Project_Brief_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Project_Plan_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Research_Foundation_v1.0.docx chore: flatten Formatted Docs folder — files now at repo root 2026-07-31 16:01:05 -04:00
Signal_Corps_Salesforce_Protocol_v1_0.docx Add Salesforce Encounter Protocol v1.0 2026-07-31 17:25:58 -04:00

Signal Corps

Internal documentation for the Signal Corps engagement methodology. Documents fall into three tiers:

  • Foundational — what Signal Corps is, why it exists, and how it works end to end
  • Protocol — what to do when a specific technical situation shows up mid-engagement
  • Policy — how Signal Corps conducts itself, regardless of situation

Foundational

Document Version
Signal_Corps_Master_Doc_v1_0.docx 1.0
Signal_Corps_Methodology_v1.0.docx 1.0
Signal_Corps_Phase1_Methodology_v2.0.docx 2.0
Signal_Corps_Project_Brief_v1.0.docx 1.0
Signal_Corps_Project_Plan_v1.0.docx 1.0
Signal_Corps_Research_Foundation_v1.0.docx 1.0
Signal_Corps_Brand_Guide_v1.0.docx 1.0

Protocol

What do I do when X occurs?

Document Version Covers
Signal_Corps_Salesforce_Protocol_v1_0.docx 1.0 Pre-engagement recon, export hierarchy (Reports → SOQL → Full Export), relationship mapping, specialist handoff triggers
Signal_Corps_AppLocked_Data_Protocol_v1_0.docx 1.0 Data locked inside SaaS apps: recon, manual download policy, API as escape hatch, lossy export detection, specialist handoff triggers
Signal_Corps_NoMetadata_DB_Protocol_v1_0.docx 1.0 Databases with missing metadata: schema archaeology, naming convention forensics, relationship inference, specialist handoff triggers

Policy

How we conduct ourselves.

Document Version
Signal_Corps_Ethical_Framework_v1.0.docx 1.0
Signal_Corps_Pre-Launch_Checklist_v1.0.docx 1.0

Backlog

Not one of the three tiers above — a holding pen for unprioritized ideas until they earn a place in the roadmap or get retired.

Document Version
Signal_Corps_Ideas_v1_0.docx 1.0

Update this index whenever a document is added, renamed, or superseded by a new version.