navidocs/STACKCP_REMOTE_ARTIFACTS_REPORT.md

StackCP Remote NaviDocs Artifacts Forensic Audit Report

Audit Date: 2025-11-27 Audit Agent: Remote Ops Inspector (Agent 2) Remote Host: ssh.gb.stackcp.com Remote Account: digital-lab.ca Deployment Status: ACTIVE

---

Executive Summary

A comprehensive forensic scan of the StackCP production deployment for NaviDocs was conducted. The scan discovered 14 active deployment artifacts across the NaviDocs directory structure. Of these:

• 12 files (85.7%) are missing from the Git repository - representing critical deployment-only artifacts
• 2 files (14.3%) match the Git repository exactly
• 0 files show hash mismatches (no deployment drift detected for files in Git)
• Total deployment size: 413 KB (aggregate)

Key Finding

The deployed NaviDocs application is NOT version-controlled in Git. The core deployment files (index.html, styles.css, script.js, and most feature components) exist only on StackCP production and would be lost if the production server is rebuilt without backup.

---

Deployment Inventory

Directory Structure

~/public_html/digital-lab.ca/navidocs/
├── index.html (36.9 KB) - MISSING FROM GIT
├── styles.css (19.5 KB) - MISSING FROM GIT
├── script.js (26.5 KB) - MISSING FROM GIT
├── brief/
│   └── index.html (68.2 KB) - MISSING FROM GIT
├── builder/
│   ├── index.html (32.3 KB) - MISSING FROM GIT
│   ├── NAVIDOCS_FEATURE_CATALOGUE.md (11.5 KB) - MATCHES GIT ✓
│   ├── riviera-meeting.html (30.9 KB) - MISSING FROM GIT
│   └── riviera-meeting-expanded.html (37.9 KB) - MISSING FROM GIT
└── demo/
    ├── index.html (12.9 KB) - MISSING FROM GIT
    ├── DEMO_SUMMARY.md (7.4 KB) - MISSING FROM GIT
    ├── CLICKABLE_DEMO_GUIDE.md (24.1 KB) - MISSING FROM GIT
    ├── DESIGN_SYSTEM_CHEATSHEET.md (8.4 KB) - MISSING FROM GIT
    ├── INTELLIGENCE_BRIEF_REDESIGN.md (41.1 KB) - MISSING FROM GIT
    └── navidocs-demo-prototype.html (28.5 KB) - MATCHES GIT ✓

File Manifest

File Path	Size	MD5 Hash	Git Status	Modified
index.html	36.9 KB	f5ee74514b71892fd9f7b19c2f462bb6	MISSING	2025-10-25 22:14:09
styles.css	19.5 KB	a2cfb903dca25a2bfcb1cadb7593535f	MISSING	2025-10-25 21:36:43
script.js	26.5 KB	fb8bf97cb3e6fbcc3082635a10e10c22	MISSING	2025-10-25 21:39:55
brief/index.html	68.2 KB	24f3bebea5cd137e20d6e936e13f7498	MISSING	2025-11-13 10:21:41
builder/index.html	32.3 KB	e2677e0581b53bf9015e92c078c9c6bb	MISSING	2025-11-13 03:23:30
builder/NAVIDOCS_FEATURE_CATALOGUE.md	11.5 KB	9d8f3e9c429177a264b3aca85a87f15f	IN GIT ✓	2025-11-14 17:27:45
builder/riviera-meeting.html	30.9 KB	7fa7c52349bddac24f67ed06fe5eb4a9	MISSING	2025-11-13 13:42:11
builder/riviera-meeting-expanded.html	37.9 KB	bd5d4d5556a75c370ca15551bc82df69	MISSING	2025-11-13 15:19:33
demo/index.html	12.9 KB	3943cf51d82934e7fd17430a0f78a451	MISSING	2025-11-13 11:07:22
demo/DEMO_SUMMARY.md	7.4 KB	b3210f99de3f3e218da43bdc62afc686	MISSING	2025-11-13 11:03:28
demo/CLICKABLE_DEMO_GUIDE.md	24.1 KB	3633a69806df12fb6513982fffab0461	MISSING	2025-11-13 11:03:11
demo/DESIGN_SYSTEM_CHEATSHEET.md	8.4 KB	a37c0228c32b804b3fe0e0e44b27621d	MISSING	2025-11-13 11:05:24
demo/INTELLIGENCE_BRIEF_REDESIGN.md	41.1 KB	41065f820d913b3560e846bccd2f31e4	MISSING	2025-11-13 11:05:36
demo/navidocs-demo-prototype.html	28.5 KB	9ac0929afef1d2c394fa20d97c6c8b83	IN GIT ✓	2025-11-13 11:04:59

---

Drift Analysis

Files Missing from Git (Critical)

12 files exist ONLY on StackCP production and are NOT version-controlled:

These files represent the core application deployment:

1. Core UI Files (3 files, 82.9 KB)

   • index.html - Main landing page
   • styles.css - Global stylesheet
   • script.js - Application JavaScript

2. Feature Components (5 files, 170.5 KB)

   • brief/index.html - Brief view UI
   • builder/index.html - Builder interface
   • builder/riviera-meeting.html - Meeting builder template
   • builder/riviera-meeting-expanded.html - Expanded meeting template
   • demo/index.html - Demo interface

3. Documentation (4 files, 80.9 KB)

   • demo/DEMO_SUMMARY.md - Demo summary
   • demo/CLICKABLE_DEMO_GUIDE.md - Clickable demo guide
   • demo/DESIGN_SYSTEM_CHEATSHEET.md - Design system documentation
   • demo/INTELLIGENCE_BRIEF_REDESIGN.md - Intelligence brief redesign docs

Files Verified in Git (OK)

2 files match the Git repository exactly - No drift detected:

1. builder/NAVIDOCS_FEATURE_CATALOGUE.md

   • Remote MD5: 9d8f3e9c429177a264b3aca85a87f15f
   • Local MD5: 9d8f3e9c429177a264b3aca85a87f15f
   • Status: ✓ VERIFIED

2. demo/navidocs-demo-prototype.html

   • Remote MD5: 9ac0929afef1d2c394fa20d97c6c8b83
   • Local MD5: 9ac0929afef1d2c394fa20d97c6c8b83
   • Status: ✓ VERIFIED

Deployment Drift Assessment

Status: NO DRIFT DETECTED for files in Git

All files that exist in both Git and remote deployment have identical MD5 hashes, confirming:

• No unauthorized modifications to deployed files
• No stale/out-of-sync versions
• Clean deployment state for tracked files

However, the majority of deployment files are untracked.

---

Git Repository Analysis

Current Git Status

Location: /home/setup/navidocs

The local Git repository contains:

• 9 agent session reports (.md files)
• Builder prompts and implementation guides
• Source code and client/server components
• Node.js dependencies (node_modules)
• Uploaded misc docs (including one matching file)

Important Note: The .gitignore file explicitly excludes:

• uploads/ - Contains uploaded files
• dist/ and build/ - Build outputs
• logs/ - Log files
• data/ - Data directories

This explains why most deployment artifacts are missing from Git - they appear to be deployment-generated or manually uploaded files that are not part of the primary source control strategy.

---

Security Assessment

Exposure Risk: MODERATE

Positive Findings:

• No API keys or credentials detected in scanned files
• No database connection strings exposed
• No sensitive configuration files (.env, credentials) found
• HTTPS deployment (verified via agents.md)
• SSH access properly secured with Ed25519 keys

Concerns:

• Single Point of Failure: 12 critical deployment files exist only on StackCP
• No Disaster Recovery: No backup version control for UI components
• Rebuild Risk: Server rebuild would require manual artifact recovery
• Documentation Drift: Demo/guide files not tracked could diverge from source

Recommendations

Immediate Priority (P0)

1. Version Control Lost Artifacts

   # Add deployment files to Git
   cd /home/setup/navidocs
   git add index.html styles.css script.js
   git add brief/ builder/*.html
   git add demo/*.md
   git commit -m "Add StackCP deployment artifacts to version control"
   

2. Create Deployment Backup Strategy

   • Automated nightly backups of /public_html/digital-lab.ca/navidocs/
   • Store backups in /home/setup/.security/backups/
   • Maintain 30-day rolling backup retention

3. Document Deployment Process

   • Create DEPLOYMENT.md documenting:
     • How files are deployed to StackCP
     • Build/generation process for missing files
     • Rollback procedures

High Priority (P1)

4. Implement CI/CD for Deployment

   • Automate deployment from Git
   • Generate/build missing files as part of CI pipeline
   • Verify deployment artifacts before going live

5. Add Content Hash Verification

   • Store MD5 hashes in Git
   • Verify production hashes match committed hashes
   • Alert on unauthorized modifications

6. Create Recovery Playbook

   • Document procedures to rebuild /navidocs/ from scratch
   • Test recovery procedures quarterly
   • Maintain offline copy of deployment scripts

---

Redis Ingestion Results

All forensic data has been ingested into Redis for archival and analysis:

Redis Database: 2 (Development/Testing) Key Prefix: navidocs:stackcp:* TTL: 30 days (auto-expiration)

Ingested Keys

Key	Type	Records	Purpose
navidocs:stackcp:metadata	Hash	1	Audit metadata
navidocs:stackcp:file:*	Hash	14	File entries with content
navidocs:stackcp:index	List	14	File inventory index
navidocs:stackcp:summary	Hash	1	Summary statistics

Query Examples

# Get audit metadata
HGETALL navidocs:stackcp:metadata

# List all scanned files
LRANGE navidocs:stackcp:index 0 -1

# Get specific file details
HGETALL navidocs:stackcp:file:index.html

# View summary statistics
HGETALL navidocs:stackcp:summary

---

Deployment Timeline

Recent Activity (October-November 2025)

Date	Time	File(s) Modified	Action
2025-10-25	21:36:43	styles.css	Initial deployment
2025-10-25	21:39:55	script.js	Initial deployment
2025-10-25	22:14:09	index.html	Initial deployment
2025-11-13	03:23:30	builder/index.html	Feature addition
2025-11-13	10:21:41	brief/index.html	Feature addition
2025-11-13	11:03:11	demo/CLICKABLE_DEMO_GUIDE.md	Documentation
2025-11-13	11:03:28	demo/DEMO_SUMMARY.md	Documentation
2025-11-13	11:04:59	demo/navidocs-demo-prototype.html	Demo artifact
2025-11-13	11:05:24	demo/DESIGN_SYSTEM_CHEATSHEET.md	Documentation
2025-11-13	11:05:36	demo/INTELLIGENCE_BRIEF_REDESIGN.md	Documentation
2025-11-13	11:07:22	demo/index.html	Feature addition
2025-11-13	13:42:11	builder/riviera-meeting.html	Feature addition
2025-11-13	15:19:33	builder/riviera-meeting-expanded.html	Feature addition
2025-11-14	17:27:45	builder/NAVIDOCS_FEATURE_CATALOGUE.md	Documentation

Deployment Status: Active and recently updated (last 44 days)

---

Forensic Summary

Audit Execution

• Remote Host: ssh.gb.stackcp.com (StackCP shared hosting)
• SSH User: digital-lab.ca
• SSH Key: Ed25519 (/home/setup/.ssh/icw_stackcp_ed25519)
• Scan Methods: SSH remote find, md5sum, file download
• Files Scanned: 14
• Scan Duration: ~2 minutes
• Data Extracted: 413 KB (all file contents)

Audit Validation

✓ SSH connection verified ✓ Directory listing complete ✓ All file hashes calculated ✓ Content downloads successful ✓ Git repository comparison complete ✓ Redis ingestion successful

Chain of Custody

All forensic data is preserved in:

1. Local copies: /tmp/stackcp_navidocs_audit/ (ephemeral)
2. Redis archive: navidocs:stackcp:* keys (30-day TTL)
3. This report: /home/setup/navidocs/STACKCP_REMOTE_ARTIFACTS_REPORT.md

---

Conclusion

The NaviDocs application is actively deployed on StackCP with recent modifications (as of November 14, 2025). The deployment consists primarily of untracked static files that would be lost if the production server were rebuilt without intervention.

Critical Action Items

This audit identifies a significant operational risk: The application depends on manual deployment processes and lacks automated version control or recovery procedures.

Recommended Next Steps:

1. Commit discovered artifacts to Git repository
2. Establish backup procedures for production deployment
3. Implement automated deployment pipeline
4. Create disaster recovery documentation

---

Report Generated: 2025-11-27 14:07:55 UTC Report Location: /home/setup/navidocs/STACKCP_REMOTE_ARTIFACTS_REPORT.md Next Review: 2025-12-27 (30 days)