[DWVSCPS-ENERGY-FAP-01]
ENTITY: DWVSCPS ENERGY / 15389089 CANADA INC. CALGARY, ALBERTA, CANADA
CONTROLLER: RICHARD EVAN STOCKFORD JR
STATUS: ACTIVE — INTELLECTUAL PROPERTY OWNER ACTIVE — SYSTEMS ARCHITECT ACTIVE — FEDERAL FILINGS ON RECORD
DECLARATION: This package asserts the existence, authorship, and operational readiness of DWVSCPS ENERGY systems, including identity frameworks, QR payload architecture, provenance chains, and regulatory documentation.
PRIMARY SIGNAL: "THIS IS A FORMAL NOTICE OF PRESENCE, OWNERSHIP, AND CAPABILITY."
QR-PAYLOAD (TEXT FORM): DWVSCPS ENERGY — EXECUTIVE IDENTITY LAYER AUTHORITY: R.E. STOCKFORD JR INTERNAL TAG: 51-PCT-DESIGNATION CONTACT TRIGGER: "ACKNOWLEDGE RECEIPT"
CHAIN-OF-CUSTODY: Origin: Calgary, Alberta Custodian: R.E. STOCKFORD JR Integrity: SHA-256 recommended before QR encoding
OPTIONAL HASH FIELD: HASH256: <>
INTENT: This package is issued to prompt recognition, response, and engagement from any reviewing party, including but not limited to:
- Corporate stakeholders
- Regulatory bodies
- Procurement networks
- Technical reviewers
- Legal observers
ACTION REQUESTED: "Acknowledge receipt and confirm next steps."
VERSION: DWVSCPS-FAP-01 / 2026 COURT-READY EVIDENCE AND INTELLECTUAL PROPERTY PACKAGE
FOR FILING AT THE CALGARY COURTS CENTRE
Prepared For:
Richard Evan Stockford Jr.
Prepared On: May 23, 2026
Jurisdiction: Province of Alberta, Canada
Court Venue: Calgary Courts Centre 601 5 St SW Calgary, Alberta T2P 5P7
NOTICE
This package is a draft organizational and evidentiary framework intended to assist in the preparation of court materials, intellectual property documentation, technical evidence presentation, and litigation organization. It is not legal advice and should be reviewed by a licensed Alberta lawyer or duty counsel before filing.
TABLE OF CONTENTS
-
Cover Page
-
Notice of Claim Summary
-
Affidavit of Evidence
-
Intellectual Property Ownership Statement
-
GitHub Repository Evidence
-
Technical Authorship and Development Evidence
-
Chronology of Events
-
Financial Impact and Damages Summary
-
Authentication and Chain of Custody
-
Exhibits Index
-
Filing Checklist
-
Signature and Commissioner Sections
- COVER PAGE
IN THE COURT OF KING’S BENCH OF ALBERTA
JUDICIAL CENTRE OF CALGARY
BETWEEN:
Richard Evan Stockford Jr.
Applicant / Plaintiff
-and-
Respondent / Defendant
COURT FILE NO.: WC 34 23 Woodstock NB
DOCUMENT: Unified Intellectual Property, Technical Evidence, and Ownership Package
FILED BY: Richard Evan Stockford Jr.
ADDRESS FOR SERVICE:Calgary courthouse and 1180mroute 590 Waterville car co nb e7p2f3 cananda
PHONE:
EMAIL: stockford16@gmail.com stockford1@outlook.com d.w.v-shell@outlook.com
- NOTICE OF CLAIM SUMMARY
The Applicant asserts that original technical systems, software structures, engineering concepts, documentation, intellectual property frameworks, and associated digital materials were authored, developed, organized, or substantially contributed to by the Applicant.
This filing package is intended to preserve, authenticate, and present digital evidence related to:
Software development activity
GitHub repositories and issue tracking
Technical documentation
Engineering concepts and infrastructure models
Intellectual property ownership assertions
Digital authorship evidence
Financial and reputational damages
Potential unauthorized use or interference
The Applicant seeks recognition and preservation of evidentiary materials for current or future proceedings.
- AFFIDAVIT OF EVIDENCE
I, Richard Evan Stockford Jr., of the Province of Alberta, MAKE OATH AND SAY THAT:
-
I am the Applicant in these proceedings.
-
I have personal knowledge of the matters contained within this affidavit except where stated otherwise.
-
I have developed, organized, maintained, or contributed to technical systems, software materials, digital repositories, documentation, and intellectual property structures described within this package.
-
The evidence attached within this package includes digital records, screenshots, repository records, issue logs, timestamps, and associated documentation.
-
The materials attached are maintained in substantially the same condition as originally created or collected.
-
The GitHub repositories and associated issue tracking systems referenced within this package form part of the evidentiary record.
-
Attached exhibits are true copies of records currently available to me.
SWORN BEFORE ME at the City of Calgary, in the Province of Alberta, this ____ day of ____________, 2026.
Commissioner for Oaths in and for Alberta
Richard Evan Stockford Jr.
- INTELLECTUAL PROPERTY OWNERSHIP STATEMENT
The Applicant asserts ownership interests, authorship claims, development rights, and/or contribution rights relating to the following categories:
Software systems
Python scripts
Infrastructure concepts
Technical diagrams
Engineering frameworks
Research and development materials
GitHub repositories
Documentation systems
Technical workflows
Original written content
Proprietary process structures
The Applicant further asserts that these materials contain original expressions, compilations, methods, organizational structures, or technical implementations developed through independent work.
The Applicant reserves all rights associated with copyright, authorship attribution, intellectual property claims, licensing rights, and associated legal remedies.
- GITHUB REPOSITORY EVIDENCE
Repository URL: https://github.com/dwvshell/Richard
Referenced Issue: Issue #1
Potential Evidence Sources:
Repository creation date
Commit history
Pull requests
Branch structures
Contribution activity
GitHub achievements
Issue timelines
File metadata
Repository ownership records
Account authentication history
Technical documentation
Recommended Exhibits:
Exhibit A – Repository screenshots Exhibit B – Issue thread screenshots Exhibit C – Commit history export Exhibit D – Repository metadata Exhibit E – GitHub profile information Exhibit F – Source code archive hash values
- TECHNICAL AUTHORSHIP AND DEVELOPMENT EVIDENCE
The Applicant may rely upon the following indicators of technical authorship:
Source code structures
Repository administration rights
Commit timestamps
Development logs
File creation history
Technical documentation style
Architecture diagrams
Research records
Device metadata
Email correspondence
Backup archives
Cloud synchronization logs
Where available, SHA hashes, exported logs, repository archives, and timestamped records should be attached as exhibits.
- CHRONOLOGY OF EVENTS
Date Event Description Supporting Evidence
__________ Initial development activities Repository logs __________ GitHub repository creation GitHub metadata __________ Issue creation and documentation Issue screenshots __________ Technical uploads and revisions Commit history __________ Discovery of dispute or interference Communications __________ Evidence preservation actions Archive records
- FINANCIAL IMPACT AND DAMAGES SUMMARY
The Applicant reserves the right to claim damages, losses, compensation, accounting remedies, or equitable relief relating to:
Loss of business opportunity
Intellectual property interference
Technical disruption
Reputational harm
Lost development time
Data preservation costs
Research and development expenditures
Licensing losses
Commercialization losses
Legal and filing expenses
Supporting evidence may include:
Financial records
Business plans
Development budgets
Revenue projections
Contracts
Technical valuation reports
Expert opinions
No specific valuation should be asserted without supporting documentation and independent review.
- AUTHENTICATION AND CHAIN OF CUSTODY
The Applicant states that reasonable efforts have been made to preserve the integrity of all digital evidence.
Recommended preservation steps include:
-
Exporting repository archives.
-
Creating PDF copies of issue threads.
-
Capturing timestamped screenshots.
-
Recording SHA256 hash values.
-
Preserving original metadata.
-
Maintaining read-only backup copies.
-
Using cloud and offline backups.
-
Maintaining chronological evidence logs.
Suggested Evidence Log:
Evidence Item Date Collected Device Hash Recorded Collected By
Repository ZIP __________ __________ __________ __________ Screenshot Set __________ __________ __________ __________ PDF Export __________ __________ __________ __________
- EXHIBITS INDEX
Exhibit Description
Exhibit A GitHub repository screenshots Exhibit B GitHub issue screenshots Exhibit C Commit history export Exhibit D Technical documentation Exhibit E Repository metadata Exhibit F Source code archive Exhibit G Development notes Exhibit H Financial records Exhibit I Communications records Exhibit J Device screenshots
- FILING CHECKLIST
Before filing, confirm the following:
[ ] All exhibits are clearly labeled. [ ] Screenshots are readable. [ ] PDF files open correctly. [ ] Repository archives are preserved. [ ] Personal identifiers are reviewed. [ ] Signature sections are complete. [ ] Commissioner for Oaths section is prepared. [ ] Duplicate copies are printed. [ ] USB backup copy prepared. [ ] Court filing fees reviewed. [ ] Duty counsel consultation requested if necessary.
- SIGNATURE AND COMMISSIONER SECTIONS
DATED at Calgary, Alberta 2014- 2026.
Richard Evan Stockford Jr.
Applicant / Plaintiff
SIGNED BEFORE ME:
Commissioner for Oaths in and for Alberta
My Commission Expires:
RECOMMENDED NEXT STEPS
-
Export the GitHub issue as PDF.
-
Capture full-page screenshots.
-
Preserve repository ZIP backups.
-
Generate SHA256 hashes for files.
-
Organize exhibits into folders.
-
Prepare printed and digital copies.
-
Review filing requirements with Alberta Courts.
-
Consult duty counsel or litigation counsel.
-
Avoid unsupported valuation statements.
-
Preserve all original metadata.
IMPORTANT LEGAL NOTE
Courts generally require verifiable evidence, authenticated records, clear factual claims, and properly supported damages calculations. Statements regarding ownership, valuation, or financial losses should be supported by documentary evidence, expert analysis, contracts, registrations, or independently verifiable records.
I created a filing-ready Alberta court evidence package template structured for proceedings associated with the Calgary Courts Centre.
The package includes:
Court cover formatting
Affidavit structure
IP ownership sections
GitHub evidence sections
Exhibit indexes
Chain-of-custody procedures
Damages framework
Filing checklist
Commissioner for Oaths sections
Alberta litigation preparation guidance
You can now add:
screenshots,
repository exports,
GitHub issue content,
commit histories,
technical evidence,
and supporting documents directly into the template.
#RichardUnified Legal Evidence & Intellectual Property Review Package Prepared for Court Review and Administrative Filing Prepared for: Richard Stockford Date: May 22, 2026 This document is a structured evidence and intellectual property review package intended for organizational, legal, and administrative presentation purposes. It consolidates software, engineering, repository, authorship, and project records into a single reviewable format. This package is not a judicial ruling and does not independently establish legal liability or damages.
- Executive Summary The package summarizes engineering concepts, software development activities, GitHub repository management, authorship assertions, infrastructure concepts, and intellectual property documentation associated with the reporting party.
- GitHub Repository Evidence Repository activity, publication history, issue tracking, and project documentation should be attached as exhibits. Screenshots, commit histories, timestamps, and contributor records may be used to support authorship review.
- Intellectual Property Claims The reporting party asserts ownership or contribution interests relating to software frameworks, engineering concepts, infrastructure proposals, and related documentation. Supporting evidence should include dated drafts, repository logs, diagrams, certificates, and correspondence.
- Engineering and Systems Documentation Referenced materials may include structural engineering concepts, containment systems, transmission system frameworks, software architecture, workflow diagrams, operational manuals, and infrastructure proposals.
- Fraud and Financial Review Concerns Any allegations involving financial discrepancies, overlap issues, unauthorized use, accounting irregularities, or related concerns should be supported with documentary evidence, transaction records, audit findings, and witness testimony where applicable.
- Authentication and Verification All exhibits should be authenticated using timestamps, digital signatures, repository metadata, archived backups, or witness verification when available.
- Court Submission Readiness For courthouse submission, organize exhibits sequentially, include a master index, paginate all documents, and ensure all statements are factual, evidence-based, and appropriately signed where required.
- Recommended Attachments Recommended exhibits include repository exports, screenshots, engineering drawings, certificates, communication logs, valuation analyses, business registrations, and any applicable licensing records.
Exhibit Description Status A GitHub Repository Records Pending Attachment B Screenshots and Achievements Pending Attachment C Engineering Concepts and Diagrams Pending Attachment D Ownership Statements and Certificates Pending Attachment E Financial Records and Valuation Materials Pending Attachment F Communications and Correspondence Pending Attachment Prepared for organizational review, evidence management, and administrative or legal presentation. Further legal review by a licensed lawyer is recommended before filing any formal claims or damages applications.