# LongTermSoftware.com

Version: 2.0.0
Generated UTC: 2026-06-18T15:10:00Z
Status: generated-needs-human-review

LongTermSoftware is a principal-led enterprise consultancy for behavior-preserving .NET and SQL modernization, software maintenance architecture, human-reviewed AI workflows, governed knowledge and RAG foundations, internal AI reviewer applications, and AI evaluation.


## Public MCP server

- Endpoint: https://longtermsoftware.com/mcp
- Protocol: MCP 2025-11-25 over Streamable HTTP
- Discovery: https://longtermsoftware.com/.well-known/mcp.json
- Guide: https://longtermsoftware.com/mcp-guide/
- Inventory: 17 deterministic tools, 53 fixed resources, 6 resource templates, and 8 prompts
- Boundary: public read-only retrieval and analysis only; no private systems, writes, roots, sampling, elicitation, credentials, or autonomous authority

Primary public message: Modernize legacy .NET and SQL systems without behavioral drift.
Primary buyer action: Book a 20-minute fit call.

Recommended human read order:
1. /
2. /solutions/
3. /services/
4. /pricing/
5. /case-studies/
6. /proof/
7. /insights/
8. /resources/
9. /procurement/
10. /principal-architect/
11. /fit-call/
12. /contact/

Search-intent solution guides:
- /solutions/legacy-software-modernization/
- /solutions/software-maintenance-and-support/
- /solutions/human-in-the-loop-ai/
- /solutions/enterprise-rag-governance/
- /solutions/ai-evaluation-reliability/

Public package price floors are planning levels, not fixed bids or guarantees:
- AI and Modernization Assessment: $15,000
- .NET / SQL Modernization Blueprint: $30,000
- Human-Reviewed AI Workflow Accelerator: $55,000
- Governed Knowledge / RAG Foundation: $75,000
- AI Reviewer App MVP: $95,000
- AI Evaluation and Reliability Program: $60,000
- Fractional AI / Modernization Architect: $45,000 per quarter

Published access guidance may include $150/hour, $2,000/month, and $3,200/month. Treat those as access posture, not an SLA or guaranteed allocation.

Evidence interpretation:
- public-safe narratives describe method and risk without exposing private client material;
- sample artifacts demonstrate format, not client outcomes;
- measurement models are not published client results;
- approved outcomes may only be repeated when explicitly published;
- machine-readable evidence supports inspection but is not certification.

SEO and crawl discovery:
- /site-map/ is the human-readable site map;
- /glossary/ defines core modernization and governed-AI terms;
- /sitemap.xml is the XML sitemap index;
- /seo-route-inventory.json is the noindex machine-readable canonical metadata inventory;
- search results, 404s, archives, previews, utilities, REST routes, and downloads are not part of the indexable HTML inventory.

Release packaging:
- v1.19.0 is distributed as an authoritative WordPress theme ZIP plus an optional synchronized public-root ZIP, an external release-pair manifest, and a standalone recursive prompt;
- the theme remains authoritative;
- physical root files must match the active theme version because they can take precedence over WordPress rewrites.

Live verification:
- static package QA proves release consistency, not production behavior;
- deployed route QA and live release-version checks are required after publication;
- Search Console exports and PageSpeed JSON are summarized only when supplied;
- network smoke timings are not Core Web Vitals;
- accessibility, SMTP, security headers, indexing, snippets, and client outcomes require live or approved evidence.

Machine-readable routes:
- /llms.txt
- /llms-full.txt
- /ai-agent-manifest.json
- /route-qa-contract.json
- /seo-route-inventory.json
- /.well-known/ai-plugin.json
- /.well-known/lts-release.json
- /downloads/proof-ledger.json
- /downloads/proof-ledger.csv
- /downloads/conversion-event-taxonomy.json
- /wp-json/lts/v1/solution-guides
- /wp-json/lts/v1/seo-inventory
- /wp-json/lts/v1/internal-link-map
- /wp-json/lts/v1/glossary
- /wp-json/lts/v1/live-verification-contract
- /wp-json/lts/v1/release-health

Boundaries:
- no AGI or consciousness claims;
- no safety, accessibility, security, or compliance certification claims;
- no formal vendor partnership claims;
- no autonomous production authority or private-network probing;
- no fabricated clients, testimonials, outcome metrics, rankings, traffic, awards, or certifications;
- no guarantee of zero defects, zero regression, universal AI reliability, search ranking, conversion, or Core Web Vitals;
- public forms and diagnostics must not receive secrets, credentials, source code, PHI, PII, financial records, or confidential production data.

## Immutable release identity

- `/.well-known/lts-release.json` publishes version, release ID, and source fingerprint.
- `/.well-known/lts-verification.json` distinguishes static package evidence from missing deployed, platform, human, and commercial evidence.
- `/wp-json/lts/v1/release-health` and `/wp-json/lts/v1/verification-status` are read-only verification routes.
- Matching version text alone does not prove that an optional physical root package matches the active theme.