USPTO
SERVICE CONTRACT · VIEW: GOV
Axiom
USPTO governs patent and trademark filings. Every filing is preflight-checked. Every conflict is documented. Every status is tracked.
Constraints
MUST: Preflight every filing before submission MUST: Run conflict clearance before trademark filing MUST: Track every serial number, application number, and status MUST: Document all examiner actions and deadlines MUST: File same-day when multiple related filings share a priority date MUST NOT: File Class 042 where conflict clearance fails MUST NOT: Submit without Declaration and Signature MUST NOT: Lose track of deadlines (Office Actions, Statement of Use, renewals)
Capabilities
CONFLICT_CLEAR, EVIDENCE_CHAIN, FILING_PREFLIGHT, STATUS_TRACK
COVERAGE: 255/255
SPEC
Scope
USPTO is the federal filing service for:
- Patents — provisional and non-provisional applications (EFS-Web)
- Trademarks — initial applications via Trademark Center (trademarkcenter.uspto.gov)
Filing Account
| Field | Value |
|---|---|
| Account holder | DEXTER DEVANAND HADLEY |
| Portal | trademarkcenter.uspto.gov |
| Entity status | Micro-entity (37 CFR 1.29) |
INTEL
Cross-Scope Evidence
| Service Claim | Evidence Source | Reference | Status |
|---|---|---|---|
| Governs patent and trademark filings | USPTO records | USPTO/CANON.md | PENDING |
| Every filing preflight-checked | Preflight process | USPTO/CANON.md | PENDING |
| Every conflict documented | Conflict clearance records | USPTO/CANON.md | PENDING |
| Every status tracked | Serial number + application tracking | USPTO/CANON.md | PENDING |
| Conflict clearance before trademark filing | Clearance process | USPTO/CANON.md | PENDING |
| All examiner actions and deadlines documented | Deadline tracking | USPTO/CANON.md | PENDING |
| Same-day filing for shared priority dates | Filing coordination | USPTO/CANON.md | PENDING |
| No Class 042 where conflict clearance fails | Clearance gate | USPTO/CANON.md | PENDING |
| No submission without Declaration and Signature | Submission checklist | USPTO/CANON.md | PENDING |
Operational Inventory
| Component | Status | Gap |
|---|---|---|
| Filing preflight process | PENDING | Verify preflight checklist |
| Conflict clearance | PENDING | Verify clearance records |
| Serial/application number tracking | PENDING | Verify tracking completeness |
| Examiner action tracking | PENDING | Verify deadline monitoring |
| Declaration and Signature verification | PENDING | Verify submission gate |
| Priority date coordination | PENDING | Verify same-day filing process |
Test
| prompt | expect | cross |
|---|---|---|
| Is every filing preflight-checked? | Yes | USPTO/CANON.md constraints |
| Can Class 042 file without clearance? | No — blocked if conflict clearance fails | USPTO/CANON.md constraints |
| Are deadlines tracked? | Yes — Office Actions, Statement of Use, renewals | USPTO/CANON.md constraints |
LEARNING
Filing Ownership Clarification
| Filing | Owner | Entity | Notes |
|---|---|---|---|
| MAMMOCHAT (SN 99439803) | Dexter Devanand Hadley | Individual (micro-entity) | PERSONAL filing. Not a UCF institutional filing. |
| CANONIC (SN 99675830) | Dexter Devanand Hadley | Individual (micro-entity) | PERSONAL filing. Not a UCF institutional filing. |
| PROV-001 through PROV-006 | Dexter Devanand Hadley | Individual (micro-entity) | PERSONAL provisional patents. Not UCF institutional filings. |
UCF vs Personal: All IP filings in this portfolio are personal filings by Dexter Devanand Hadley as an individual inventor and applicant. These are NOT filed through, owned by, or assigned to the University of Central Florida (UCF). The micro-entity status (37 CFR 1.29) applies to Dexter as an independent individual filer.
UCF Duplicate Filing — MAMMOCHAT (SN 99445546)
CRITICAL: UCF filed a duplicate MAMMOCHAT trademark application 2 days after Dexter’s personal filing.
| Field | Dexter (SN 99439803) | UCF (SN 99445546) |
|---|---|---|
| Filed | Oct 13, 2025 (FIRST) | Oct 15, 2025 |
| Applicant | Dexter Devanand Hadley (Individual) | University of Central Florida Board of Trustees |
| Entity | Micro-entity | State University (Florida) |
| Classes | 009 | 009, 042, 044 (expanded) |
| Mark Type | Trademark | Trademark + Service Mark |
| Basis | 1(b) Intent to Use | 1(b) Intent to Use |
| Counsel | Pro se | Amber N. Davis, Savvy IP Law (docket 10669-440) |
| Address | — | 4365 Andromeda Loop N., Suite 360, Orlando, FL 32816 |
| Status | OFFICE ACTION (2(e)(1), 2026-03-02) | Awaiting Examination |
UCF Goods/Services (Expanded)
| Class | UCF Description | Dexter Description |
|---|---|---|
| 009 | Downloadable computer application software for mobile phones and handheld computers, namely, software for women suffering from breast cancer for purposes of communicating with other women with breast cancer and providing information about health and wellness, namely, related to breast cancer awareness, prevention, treatment, and clinical studies | Downloadable mobile applications for retrieving and displaying health information |
| 042 | Providing a web hosting platform for women suffering from breast cancer for purposes of communicating with other women with breast cancer and providing information related to breast cancer awareness, prevention, treatment and clinical studies; Platform as a service (PAAS) services featuring software platforms for the transmission of information related to breast cancer awareness, prevention, treatment and clinical studies | (not filed) |
| 044 | Providing a website featuring information about health and wellness, namely, related to breast cancer awareness, prevention, treatment, and clinical studies | (not filed) |
Conflict Analysis
- Priority: Dexter filed first (Oct 13 vs Oct 15). Dexter holds constructive use priority under 15 U.S.C. 1057(c).
- Overlap: Both applications claim Class 009 for MAMMOCHAT. Direct conflict.
- UCF expanded: UCF added Classes 042 (PaaS) and 044 (health info website) — classes Dexter did not file. UCF’s Class 009 description is also far more specific (breast cancer focus vs generic health info).
- Examiner assignment: When UCF’s application reaches examination, the examiner MUST cite Dexter’s prior-filed application as a potential conflict under Section 2(d).
- The 2(e)(1) refusal complicates this: If Dexter’s application is refused and abandoned, UCF’s application may proceed unchallenged in Class 009. The Office Action response is now doubly critical — it defends not just Dexter’s mark but his priority position against UCF’s duplicate.
Strategic Implications
- Dexter MUST respond to the Office Action (OA-001) to maintain priority
- UCF filing through outside counsel (Savvy IP Law) suggests institutional IP strategy
- The expanded claims (042, 044) cover services Dexter did not claim — UCF is trying to capture the full service footprint
- Dexter’s response strategy should also consider whether to amend his application to add Classes 042 and 044 (requires new filing or amendment)
Correspondence Log
2026-03-02 — Inbound (4 emails)
| # | From | Subject | Auth | Verdict |
|---|---|---|---|---|
| COR-001 | TMOfficialNotices@uspto.gov | Non-Final Office Action — SN 99439803 (MAMMOCHAT) | DKIM @uspto.gov PASS, DMARC PASS, SPF PASS (amazonses.uspto.gov) | LEGITIMATE |
| COR-002 | usptotrademarkalert@gmail.com | Trademark Registration — $899 payment demand (CANONIC) | Gmail origin, no USPTO authentication | SCAM |
| COR-003 | noreply@uspto.xn–gv-68s (punycode) | Section 8/15 Declarations — CANONIC | Bounce via uspto-filings.org (89.117.60.137), punycode-spoofed From domain | SCAM |
| COR-004 | noreply@uspto.xn–gv-68s (punycode) | Section 8/15 Declarations — CANONIC (duplicate) | Same as COR-003 | SCAM |
Scam Pattern Analysis
| Indicator | COR-002 | COR-003/004 |
|---|---|---|
| From domain | @gmail.com (not @uspto.gov) | @uspto.xn–gv-68s (punycode spoof) |
| Envelope-From | gmail.com | bounce@uspto-filings.org |
| Sending IP | Google SMTP | 89.117.60.137 |
| Urgency tactic | $899 fee demand | “24 hours or abandonment” |
| Fake contact | Payment link (liv-e.online/fee-899) | “Aaron Michael Daniels” at legalipadvisor.net, (571) 249-3615 |
| DKIM | None (gmail only) | None (no DKIM for uspto.gov) |
| Serial cited | 99675830 (CANONIC) | 99675830 (CANONIC) — fake serial appended |
| Attachment | None | “Non-Final Office Action” PDF (malicious) |
Key lesson: Real USPTO emails come from @uspto.gov with DKIM signatures from uspto.gov. Any email claiming USPTO origin without DKIM @uspto.gov is fraudulent. USPTO states they never contact applicants by phone. Scammers target newly filed marks within days of public appearance on TSDR.
Office Action Register
OA-001: MAMMOCHAT — Non-Final Office Action
| Field | Value |
|---|---|
| Serial | 99439803 |
| Mark | MAMMOCHAT |
| Issue date | 2026-03-02 |
| Examiner | Mindy Wudarsky |
| Law Office | LO117 — LAW OFFICE 117 |
| Phone | (571) 272-5672 |
| Mindy.Wudarsky@uspto.gov | |
| Response deadline | 2026-06-02 (3 months) |
| Extension available | 1 x 3-month extension to 2026-09-02 |
| 99439803.pdf (16 pages) |
Refusal: Section 2(e)(1) — Merely Descriptive
The examiner refused MAMMOCHAT under Section 2(e)(1) of the Trademark Act (15 U.S.C. 1052(e)(1)) as merely descriptive of the applied-for goods.
Examiner’s argument:
- MAMMO = informal shortened form of “mammogram” (breast X-ray examination)
- CHAT = synchronous exchange of remarks over a computer network
- Combined meaning: “an exchange of remarks relating to mammograms”
- Consumers would immediately understand the mark describes a feature/purpose of the software
Evidence cited by examiner:
- Dictionary.com — “mammo” definition
- AHDictionary.com — “mammogram” definition
- AHDictionary.com — “chat” definition
- mammochat.com website — applicant’s own site describes “empathic AI to help women navigate breast health screenings”
Positive finding: No conflicting marks found in search.
Response Strategy: Argue Suggestive (Not Descriptive)
MAMMOCHAT is suggestive, not merely descriptive. The response should argue:
-
Imagination gap: A consumer encountering “MAMMOCHAT” must exercise imagination to connect it to “AI-assisted breast health screening navigation.” The mark does not immediately convey the full nature of the goods.
-
MAMMO is not an established standalone word: “Mammo” is a Latin prefix (mamma = breast). The examiner’s cited source lists it as informal — not an established dictionary entry with independent meaning. It requires a cognitive step to connect “mammo” to “mammogram.”
-
CHAT does not describe the software’s function: The software does not merely “chat about mammograms.” It uses AI to navigate complex health screening pathways, interpret clinical workflows, provide emotional support, and guide patients through medical decisions. “Chat” does not describe these functions.
-
Composite creates new meaning: MAMMOCHAT is a coined portmanteau. Like MICROSOFT (microcomputer + software), INSTAGRAM (instant + telegram), or SNAPCHAT (snap + chat) — all registered on the Principal Register — the combination creates a distinct commercial impression that requires a mental leap.
-
Third-party registrations: SNAPCHAT (Reg. 4,866,669) and LIVECHAT (Reg. 4,563,889) are registered on the Principal Register despite containing “CHAT.” This shows “CHAT” in combination does not automatically render a mark descriptive.
-
Dexter IS the instance: The applicant is the inventor of the governed AI system. MAMMOCHAT names a specific governed instance — not a generic category. It is the proper noun for a particular AI implementation, not a description of any chat about mammograms.
-
Services IS the class: MAMMOCHAT is filed in Classes 009, 042, AND 044. The examiner’s descriptiveness analysis focused narrowly on Class 009 (downloadable apps). But Classes 042 (SaaS/software services) and 044 (healthcare services) cover services, not just goods. The mark does not describe the services — it identifies the source. A “mammochat” does not describe a healthcare service; it names one. The gap between “MAMMOCHAT” and the actual services (AI-governed credential verification, clinical workflow navigation, patient empowerment) requires imagination, not mere recognition.
Deadlines
| Deadline | Date | Action |
|---|---|---|
| Response due | 2026-06-02 | File response via TEAS |
| Extension request | 2026-06-02 | Request 3-month extension if needed |
| Final deadline (with extension) | 2026-09-02 | Absolute last date |
| Abandonment | After final deadline | Mark abandoned if no response |
| *LEARNING | USPTO | 1 LEGITIMATE + 3 SCAM | OA-001 MAMMOCHAT 2(e)(1) | 2026-03-02* |
ROADMAP
VOCAB
| Term | Definition |
|---|---|
| PREFLIGHT | Pre-submission clearance gate for filings. |
INHERITANCE CHAIN
SERVICES
SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.
MUST: Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST: Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST: Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST: Discover SERVICE scopes from filesystem only (no manual catalog)
MUST: Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST: CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON (nothing else)
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST: SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST: VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST: Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST: Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST: Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence
hadleylab-canonic
HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.
MUST: Every app, book, paper, deal, or patent is evidence of MAGIC MUST: All scopes inherit canonic-canonic/CANONIC.md governance MUST: All users governed under USERS/ via SERVICES/USER MUST: Cross-index INTEL across users (INTEL.md) MUST: Shared events propagate to ALL affected user dashboards MUST: Maintain governance workspace purity (.md files only) MUST: Ledger all COIN (validated work) through MAGIC 255 MUST: Compile all INTEL from governed sources MUST: Keep frontend/runtime implementation under ~/.canonic (hidden runtime) MUST: Surface governed TALK, Library, and SERVICES scopes (no orphan content) MUST: Derive nav labels from governed scope names (no hardcoded strings) MUST NOT: Publish without governance (CANON.md required) MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN MUST NOT: Silo intelligence inside a single user when multiple are affected MUST NOT: Expose VAULT contents outside NDA scope MUST NOT: Store runtime artifacts in governance workspace
canonic-canonic
SPEC is governance. `canonic-canonic/` is the spec root.
MUST: Keep this repo governance-only (.md/.pdf) MUST: Publish workspace mapping in CANONIC.git (no hardcoded repo lists) MUST: Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/) MUST: Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic) MUST NOT: Embed beta-test app URLs in platform page content