added
This commit is contained in:
eddiesoehnel
parent
b021bb1ff7
commit
6cbdb6d23f
|
|
@ -1,2 +1,3 @@
|
|||
|
||||
pid skill: LOD emails and posts
|
||||
browser history
|
||||
|
|
|
|||
0
eddie-soehnel-additional-signals.md
Normal file
0
eddie-soehnel-additional-signals.md
Normal file
|
|
@ -22,6 +22,8 @@
|
|||
- [ENDORSEMENTS AND TESTIMONIALS](#endorsements-and-testimonials)
|
||||
- [METADATA, ONTOLOGY AND CONTEXT](#metadata-ontology-and-context)
|
||||
- [WHAT I HAVE:](#what-i-have)
|
||||
- [Strategic Assets](#strategic-assets)
|
||||
- [Tactical Assets](#tactical-assets)
|
||||
- [WHAT I NEED:](#what-i-need)
|
||||
- [Open To](#open-to)
|
||||
- [Match Context](#match-context)
|
||||
|
|
@ -195,18 +197,37 @@ In this model, information becomes a multiplier. It amplifies human capability,
|
|||
|
||||
## WHAT I HAVE:
|
||||
|
||||
### Strategic Assets
|
||||
|
||||
* Published tools with predictions and action plans to help people position for massive change as we transition into the next economic supercycle. See [https://EddieSoehnel.com/FutureMap](https://eddiesoehnel.com/mte-prediction-framework/)
|
||||
* Published tools for brands to understand and adopt token technology/web3. See [https://EddieSoehnel.com/TokenTech](https://eddiesoehnel.com/tokentech/)
|
||||
* Published tools on starting and scaling B2C and B2B2C businesses using an exponential growth strategy that I’ve successfully applied three times.[https://EddieSoehnel.com/DTCForConsumerBrands](https://EddieSoehnel.com/DTCForConsumerBrands)
|
||||
* An extensive knowledgebase with text, video, infographics and other tools to help dog owners positively impact the lives of their pets through my pet business at [https://TheLightofDog.com/](https://thelightofdog.com/)
|
||||
* I am building a spec-driven, AI-native product development operating system where structured Markdown (knowledge layer) defines the system, AI agents execute against it to generate and run the product (execution layer), and data feeds back to continuously improve it—making the repository itself an executable blueprint for both digital and physical product creation. This represents a new methodology for creating products and services, as AI becomes the primary execution and production layer. AI is no longer limited to writing code; it is increasingly capable of conducting research, running tests, generating new materials, prototyping products, and operating automated production systems. As a result, new paradigms are emerging for how we communicate intent to AI. This product development OS is my approach to structuring that communication—translating strategy into executable specifications that AI can reliably interpret and act upon. [It is published here](https://projects.eddiesoehnel.com/adminprojects/product-dev-os).
|
||||
* A framework that defines a system ontology approach where a complex software system is modeled as a structured graph (nodes and relationships) that serves as the single source of truth—allowing AI to automatically generate diagrams, detect issues, simulate changes, and even build code. It’s important because it transforms system design from static documentation into a machine-readable, AI-operable model, enabling automation, consistency, and far more intelligent development and scaling of software systems. [It is published here](https://projects.eddiesoehnel.com/adminprojects/product-dev-os).
|
||||
* A future-proof data platform — already deployed in one of my businesses — where the data is the application. It’s portable, AI-native, and policy-driven, so the data itself defines structure, relationships, actions, and even its UI. That eliminates rigid databases, reduces dependency on static screens, and avoids cloud lock-in. The payoff: dramatically lower cost and complexity, and far greater power as AI becomes the primary operating system for everything. I have a conceptual and architectural framework document that defines guiding principles, emerging patterns and baseline specifications. [See it here](https://docs.google.com/document/d/1YruyY2anFoBRVHTLEdqGhx-CKPHtctMUtkcLs6GBQQY/edit?usp=sharing)
|
||||
* A public repository documenting a personal edge data center architecture, including its hardware tiers, VM strategy, networking, security practices, backup and disaster recovery procedures, monitoring, power resilience, and solar support infrastructure. It serves as the canonical planning and operations reference for building and maintaining a local-first, AI-ready infrastructure stack across development, production, and standby systems. [See it here](https://projects.eddiesoehnel.com/adminprojects/edge-data-center-main-OPEN)
|
||||
* Excess on-site solar generation, redundant terrestrial and satellite internet, and generator-backed power enable sovereign edge data center hosting in a secure, resilient location outside major metro areas.
|
||||
* Published tools on Findability In The AI Era, for members of the iNDX community at [https://Community.iNDX.earth/](https://community.indx.earth/) Core tools include [Findability In The AI Era: Master Framework](https://docs.google.com/document/d/1HfdNZRC4823NvT1ID2ZQNrcW8PCT4czUlnIXROLY_20/edit?usp=sharing) and [Portable Identity Document (PID) Template](https://docs.google.com/document/d/1zcdaWYdqMUOXu690om0NfgJ0-mf0lyyBQw6rKeg7uKM/edit?usp=sharing)
|
||||
* Published tools for brands to understand and adopt token technology/web3. See [https://EddieSoehnel.com/TokenTech](https://eddiesoehnel.com/tokentech/)
|
||||
* Published tools with predictions and action plans to help people position for massive change as we transition into the next economic supercycle. See [https://EddieSoehnel.com/FutureMap](https://eddiesoehnel.com/mte-prediction-framework/)
|
||||
* Published tools on starting and scaling B2C and B2B2C businesses using an exponential growth strategy that I’ve successfully applied three times.[https://EddieSoehnel.com/DTCForConsumerBrands](https://EddieSoehnel.com/DTCForConsumerBrands)
|
||||
* An extensive knowledgebase with text, video, infographics and other tools to help dog owners positively impact the lives of their pets through my pet business at [https://TheLightofDog.com/](https://thelightofdog.com/)
|
||||
* I have many more projects, skills, workflows and tools published on [my Git platform](https://projects.eddiesoehnel.com/adminprojects)
|
||||
* More tools published in this document.
|
||||
* Published tools on Findability In The AI Era. Core tools include:
|
||||
- [Findability In The AI Era, Covering SEO/GEO: Master Framework](https://projects.eddiesoehnel.com/adminprojects/seo-geo-OPEN)
|
||||
- [Portable Identity Document (PID) Template](https://projects.eddiesoehnel.com/adminprojects/portable-identity-document-template-OPEN): A resume is optimized for human attention. A PID is optimized for AI comprehension, discovery, and matching in the AI era. The PID is what we will evolve to using for networking and finding opportunities.
|
||||
- [Structured Website Builder](https://projects.eddiesoehnel.com/adminprojects/structured-website-builder-OPEN) A tool that builds a highly structured website optimized for SEO and GEO for the AI agentic era.
|
||||
- [Marketing Email System](https://projects.eddiesoehnel.com/adminprojects/email-campaigns-prod-app-OPEN). A multi-brand email campaign operations system for the AI era using Listmonk and Postmark, including HTML campaigns, welcome emails, open/click tracking, non-open follow-ups, exports, backups, and future segmentation/automation planning.
|
||||
* Not just ideas about AI-native systems, but also working patterns of turning them into repos, skills, deterministic scripts, public templates, private ops docs, receipts, and repeatable workflows.
|
||||
|
||||
### Tactical Assets
|
||||
|
||||
* A framework that defines a system ontology approach where a complex software system is modeled as a structured graph (nodes and relationships) that serves as the single source of truth—allowing AI to automatically generate diagrams, detect issues, simulate changes, and even build code. It’s important because it transforms system design from static documentation into a machine-readable, AI-operable model, enabling automation, consistency, and far more intelligent development and scaling of software systems. [It is published here](https://projects.eddiesoehnel.com/adminprojects/product-dev-os).
|
||||
* A Git-backed personal operating system rooted in `C:\projects`, with project repositories, source-controlled Markdown, task workflow logs, publication receipts, skill files, infrastructure inventories, and Google Drive/JSON/NAS/email sources treated as inputs for AI-assisted recall and updates.
|
||||
* A daily operating and memory-capture workflow that connects task planning, audio logs, project changelogs, CRM/JSON records, calendar review, Git updates, media processing, backups, and AI-assisted prompts into one recurring review loop.
|
||||
* concrete AI-native knowledge-structuring architecture that separates human-readable Markdown/HTML from AI-readable chunks, Q&A, CIS/chunk-intelligence signatures, control-plane metadata, discovery files, versioning, policy overlays, and future vector/graph enrichment.
|
||||
* Deterministic website-publishing scripts that sync authored content to Hugo, build AI discovery indexes, generate root discovery files, and publish Hugo output while preserving key machine-readable files.
|
||||
* A website content-structuring skill stack for authoring, chunking, semantic Q&A generation, AI index/discovery materialization, HTML semantic artifact checks, contact-form deployment, and conversion of the builder to new website projects.
|
||||
* A repeatable private-to-public publication workflow for sanitizing operational repos into useful public templates, including explicit source/file gates, anonymization maps, leak scans, validation tiers, ratchet artifacts, and publication receipts.
|
||||
* Email intelligence scripts for exporting Listmonk data, pulling Postmark telemetry, backing up Listmonk, sending welcome emails, and analyzing LOD/iNDX non-open segments for follow-up campaigns.
|
||||
* Operational scripts and app maintenance utilities, including payment counter reseeding, file path migration, customer data repair, API app work, and AI OS/spec structure.
|
||||
* Miscellaneous skill and productivity tool library with reusable prompt/workflow skills for publication, product analysis, brainstorming, bias avoidance, autonomous large-build management, database search beyond Google, Google Docs Markdown conversion with images, Garmin FIT extraction, and Git/Gitea release processes.
|
||||
* A ratchet-based skill framework and skill-template repo for turning recurring agent mistakes, workflow lessons, validation gaps, and review patterns into durable skill instructions, checklists, fixtures, and anti-patterns.
|
||||
* A Google Docs Markdown conversion workflow with image extraction support, useful for moving cloud-authored long-form documents into Git/Markdown workflows while preserving media.
|
||||
|
||||
## WHAT I NEED:
|
||||
|
||||
|
|
@ -1056,3 +1077,7 @@ Transparent (PNG) image link: [https://EddieSoehnel.com/ProfilePicPNG](https://e
|
|||
[image1]: /assets/images/eddie-soehnel-portable-identity-document-and-chronicle-image1.png
|
||||
|
||||
[image2]: /assets/images/eddie-soehnel-portable-identity-document-and-chronicle-image2.png
|
||||
|
||||
# **ADDITIONAL SIGNALS**
|
||||
|
||||
I maintain a 3-month snapshot from my Hub database—an object-oriented JSON system I built as the nerve center of my life. It captures my daily activities as a searchable memory layer, helping me surface signal, trends, and insights that get lost in day-to-day noise. What follows is a filtered view of what I’ve chosen to make public: what I’m learning, reading, thinking about, and working on and anything else I find interesting. I update this weekly with recent additions. Entries here:
|
||||
284
review-drafts/PID-update-review-draft-2026-06-16.md
Normal file
284
review-drafts/PID-update-review-draft-2026-06-16.md
Normal file
|
|
@ -0,0 +1,284 @@
|
|||
# PID Update Review Draft
|
||||
|
||||
Agent response to human when PID update review draft is complete: This is a draft for your review before anything is added to your Portable Identity Document (PID).
|
||||
|
||||
Please edit freely:
|
||||
- delete anything that should not be included
|
||||
- correct anything inaccurate
|
||||
- add missing context, links, examples, names, or proof
|
||||
- mark private items that should be removed or generalized
|
||||
- strengthen anything that feels too vague or too narrow
|
||||
|
||||
After you edit this draft, ask the agent to continue from your revised file and update your PID.
|
||||
|
||||
If your edits reveal a recurring preference, missing category, privacy rule, source type, or better way to describe your work, ask the agent to adjust the PID update maintenance skill so future runs improve.
|
||||
|
||||
## Run Scope
|
||||
|
||||
- Timeframe reviewed: June 6, 2026 through June 16, 2026.
|
||||
- Approved sources reviewed: `C:\Users\edsoe\My Drive` and `C:\projects`.
|
||||
- PID source reviewed: `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md`.
|
||||
- Privacy posture used: standard privacy. Health, family, client, financial, legal, account, credential, and private operational details were generalized, excluded, or converted into review questions.
|
||||
- PID update status: awaiting user review. Nothing has been appended to the PID.
|
||||
|
||||
## SUMMARY / FOCUS
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Recent work sharpened the thread connecting iNDX, PaddleNet, PIDs, AI-native networking, and local personal AI infrastructure: the PID is emerging as the structured communication layer that local agents can use to represent people, discover matches, and coordinate opportunities without relying on traditional platform profiles.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-business\specs\1_strategy_s\nsig-vision-strategy.md`; Google Drive doc `Decentralized AI-Native Professional Networking`, updated June 6, 2026; `C:\projects\indx\portable-identity-document-template-OPEN\CHANGELOG.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Continued building toward a Personal AI Operating System (PaiOS) / Alexandria model where local memory, structured event logs, indexed files, STT transcripts, CRM data, and agent skills form a durable "digital Eddie" capable of strategic support, relationship nudging, research recall, and task execution.
|
||||
- Evidence: Google Drive doc `ALX: Personal AI Operating System (PaiOS)`, updated June 12, 2026; `C:\projects\1-flows\flows\daily-log.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. The public PID should describe the architecture and goals, not private data sources or sensitive implementation details.
|
||||
|
||||
## METADATA, ONTOLOGY AND CONTEXT / WHAT I HAVE
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] An updated PID template and maintenance workflow that now treats a PID as a living, review-first, evidence-backed identity layer, including maturity-model thinking, initial-creation and update-maintenance skills, run receipts, and stronger source-permission gates.
|
||||
- Evidence: `C:\projects\indx\portable-identity-document-template-OPEN\CHANGELOG.md`; `C:\projects\indx\portable-identity-document-template-ADMIN-for-open\tasks\2026-06-15-pid-repo-development.md`; `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\skills\PID-update-maintenance-skill.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A working iNDX/PaddleNet NetworkSIG concept that separates identity data, orchestration logic, inference, telemetry, trust/freshness/permission signals, and local-agent processing. The current direction includes local user agents pulling PID links, submitting telemetry, and using their own inference to identify matches.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-business\specs\1_strategy_s\nsig-vision-strategy.md`; `C:\projects\paddlenet\paddlenet-app\paddlenet-nsig\paddlenet-nsig-pid-ingestion\3_product_development_s\gate access by requiring telemetry upload.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] An open-source AI-era findability stack that now includes a structured website builder, SEO/GEO framework, semantic discovery files, agent/discovery metadata, and email campaign tooling that can be adapted by brands or industry communities.
|
||||
- Evidence: `C:\projects\publication-receipts-to-open\2026-06-09-structured-website-builder-publication-receipt.md`; `C:\projects\publication-receipts-to-open\2026-06-11-email-campaigns-prod-app-publication-receipt.md`; `C:\projects\indx\indx-front-website\tasks-workflows\2026-06-09-new-published-files-and-changes.md`; `C:\projects\productivity\seo-geo-OPEN\README.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A repeatable email intelligence and non-open analysis workflow for iNDX campaigns, adapted from the LOD workflow, with Listmonk export scripts, Postmark telemetry pulls, analyzer fixes, and a one-command campaign workflow.
|
||||
- Evidence: `C:\projects\productivity\email-campaigns-prod-app\tasks-workflows\2026-06-11-indx-non-opens-process-implementation.md`; public receipt `C:\projects\publication-receipts-to-open\2026-06-11-email-campaigns-prod-app-publication-receipt.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe if described generally; exclude recipient counts or private campaign data unless approved.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A practical edge-compute and resilience stack powered by local infrastructure, solar, UPS/runtime planning, recycled hardware, server/VM documentation, Cloudflare/Gitea/Caddy routing, fleet scans, and private VM deployment workflows.
|
||||
- Evidence: JSON records `5941`, `5946`, `5963`; `C:\projects\infra\edge-data-center-main\external-software-tools-repos.md`; `C:\projects\infra\edge-data-center-main\README.md`; Google Drive doc `Energy As Currency Via kWh`; Google Drive doc `Kilowatt Hour Consumption Check`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Public PID should avoid private hostnames, IPs, keys, network layout, and exact security posture.
|
||||
|
||||
## METADATA, ONTOLOGY AND CONTEXT / WHAT I NEED
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] A development or implementation partner may be useful for accelerating NetworkSIG/PaddleNet from rich concept and prototype architecture into a working user-facing system, especially around secure PID ingestion, matching, telemetry, privacy, and local/cloud orchestration.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-business\specs\1_strategy_s\nsig-vision-strategy.md` premortem and plan sections; JSON record `5946` references iNDX moving slowly due to infrastructure and development constraints.
|
||||
- Confidence: Medium.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] The PTC/SIA innovation sprint concepts would benefit from operational collaborators who can help source problem statements, recruit students/technologists, manage event logistics, capture outputs, and convert event material into AI-ingestable industry knowledge.
|
||||
- Evidence: Google Drive docs `PTC 2026 Innovation Directive`, `PTC Innovation Directive`, `PTC Innovation Directive: Core Format = Innovation Sprint Ops Manual`; `C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Question] Do you want the PID to explicitly say you are open to paid consulting or fractional work as an "AI integration / automation specialist" for small businesses, associations, or consumer/outdoor brands?
|
||||
- Evidence: June 8 transcript says you were thinking about positioning around AI integration/automation, reducing costs, and making work faster/better for others.
|
||||
- Confidence: Medium.
|
||||
- Privacy: Safe, but needs your wording.
|
||||
|
||||
## METADATA, ONTOLOGY AND CONTEXT / OPEN TO
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Open to helping outdoor, paddlesports, snowsports, and consumer-product communities run practical AI innovation programs: hackathon-style sprints, innovation challenges, problem discovery surveys, student/technologist recruiting, and post-event AI-ingestible knowledge libraries.
|
||||
- Evidence: Google Drive `PTC 2026 Innovation Directive`; `C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] Open to collaborations around local-first personal AI, memory architecture, AI agents, PID/network matching systems, and trusted discovery infrastructure.
|
||||
- Evidence: Google Drive `ALX: Personal AI Operating System (PaiOS)`; Google Drive `Decentralized AI-Native Professional Networking`; `C:\projects\paddlenet\paddlenet-business\specs\1_strategy_s\nsig-vision-strategy.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## METADATA, ONTOLOGY AND CONTEXT / MATCH CONTEXT
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Ideal collaborators include industry association leaders, outdoor-sector operators, technologists, students, AI builders, local-first software developers, privacy/security thinkers, and community organizers who want to turn emerging technology into practical tools, events, and shared industry assets.
|
||||
- Evidence: PTC Innovation Directive docs; SIA proposal; NetworkSIG strategy docs.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] Strong match opportunities may exist with associations or niche industries that need practical AI adoption programs but lack internal capacity to translate vague AI interest into usable workflows, scripts, content systems, innovation sprints, or structured knowledge repositories.
|
||||
- Evidence: PTC Innovation Directive, SIA proposal, iNDX email/workflow automation files.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## MY INTERESTS AND FOCUS / AI, DATA & AGENT SYSTEMS
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Recent research and tool tracking focused on agent memory, MCP, local-first personal AI, AI observability, secure agent execution, codebase knowledge graphs, agent skill ecosystems, and privacy-preserving infrastructure.
|
||||
- Evidence: `C:\projects\infra\edge-data-center-main\external-software-tools-repos.md`; Google Drive `ALX: Personal AI Operating System (PaiOS)`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Developed the idea that future networking shifts from attention-based self-promotion to signal-based discovery: the PID becomes a rich, authentic, machine-readable signal of who someone is, what they have, what they need, what they know, and where they are headed.
|
||||
- Evidence: Google Drive `Decentralized AI-Native Professional Networking`, section `Stop Beating Our Chests For Attention`; PID template changelog June 2, 2026.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## MY INTERESTS AND FOCUS / BUSINESS, STRATEGY & GROWTH SYSTEMS
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Continued building an outdoor brand intelligence practice based on scanning brand emails for strategic signals such as workwear/outdoor convergence, product-system architecture, material provenance, circularity, repair/resale/refill, participation systems, and brand-as-media behavior.
|
||||
- Evidence: Google Drive `2026 06 15 Outdoor Brand Innovation Intelligence Report`; Google Drive `2026-05-25-outdoor-brand-innovation-email-intelligence`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Proposed adapting PTC innovation programming ideas to SIA, including future decks, an innovation sprint, AI-era findability sessions, and open-source toolkits for structured websites and email systems.
|
||||
- Evidence: `C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Include only if this outreach/proposal is not confidential.
|
||||
|
||||
## MY INTERESTS AND FOCUS / ECONOMICS, FINANCE & MACRO SYSTEMS
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Recent Future Map notes and posts explored AI-driven job unbundling, the possibility of more smaller companies with fewer employees, retail investors as exit liquidity in AI-related IPOs, balance-sheet-driven consumer spending, China demographics/automation, equity valuation risk, office/manufacturing vacancies, and spending supported by generational wealth transfer.
|
||||
- Evidence: JSON records `5937`, `5945`, `5948`, `5952`, `5955`, `5956`, `5957`, `5965`; `C:\projects\future-map\future-map\notes.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Advanced the "energy as currency via kWh" framework, clarifying kWh as a unit of account and pricing denominator for energy-constrained services rather than a store of value, with market clearing and service-layer outcome attestation determining value.
|
||||
- Evidence: Google Drive `Energy As Currency Via kWh`, updated June 12, 2026; JSON record `5961`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## MY INTERESTS AND FOCUS / ENERGY, INFRASTRUCTURE & COMPUTE
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Continued expanding the local sovereign edge-compute model by converting donated older computers into Linux/server infrastructure, documenting hardware/software assets, improving VM access, planning UPS/runtime, reducing solar sell-back faults, and using solar-powered compute as a practical testbed for energy-aware infrastructure.
|
||||
- Evidence: JSON records `5932`, `5941`, `5946`, `5963`; June 8 transcript; `C:\projects\infra\edge-data-center-main\external-software-tools-repos.md`; Google Drive `Kilowatt Hour Consumption Check`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Public description should avoid operationally sensitive details.
|
||||
|
||||
## MY INTERESTS AND FOCUS / INNOVATION, FUTURE & FORESIGHT
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Recent foresight work increasingly frames innovation as a practical operating system for industries: identify real problems, bring in students/technologists, use AI to prototype workflows or scripts, capture the outputs, publish them as shared knowledge, and repeat.
|
||||
- Evidence: Google Drive PTC Innovation Directive docs; `C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] A recurring thesis is that industries can either be dragged through AI adoption as passive recipients or deliberately build their own experimentation pipelines, knowledge libraries, and toolkits before platform dependency hardens.
|
||||
- Evidence: PTC Innovation Directive, SIA proposal, Future Map notes, structured website/email publication receipts.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## PERSONALITY / MY STYLE
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] Recent work reinforces a pattern of turning personal operating friction into repeatable systems: daily logs, audio logs, JSON activity records, Git-backed project updates, cloud documents, receipts, skill ratchets, and structured workflows.
|
||||
- Evidence: `C:\projects\1-flows\flows\daily-log.md`; JSON activity records; PID maintenance skill edits; publication receipts.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe if generalized.
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] The recent activity pattern shows a strong preference for open-sourceable, reusable artifacts: frameworks, skills, templates, playbooks, publication receipts, sanitized public repos, and operating manuals.
|
||||
- Evidence: structured website builder publication receipt; email-campaigns publication receipt; PID template changelog; PTC ops manuals.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## PROFESSIONAL CHRONICLE / iNDX
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] In June 2026, advanced iNDX/PaddleNet infrastructure by publishing a new iNDX community summary, rebuilding semantic discovery files, adding agent/discovery metadata, correcting stale paths, improving page metadata, and aligning iNDX publishing practices with the PaddleNet website workflow.
|
||||
- Evidence: `C:\projects\indx\indx-front-website\tasks-workflows\2026-06-09-new-published-files-and-changes.md`; git logs for `C:\projects\indx\indx-front-website`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Sent or supported the June 9 iNDX campaign around PaddleNet findability work, then built a non-open analysis workflow using Listmonk exports and Postmark telemetry to identify delivered non-open recipients for follow-up.
|
||||
- Evidence: JSON record `5949`; `C:\projects\productivity\email-campaigns-prod-app\tasks-workflows\2026-06-11-indx-non-opens-process-implementation.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Do not include private recipient data.
|
||||
|
||||
## PROFESSIONAL CHRONICLE / FUTURE MAP
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Drafted a proposal for SIA adapting Future Map, PTC Innovation Sprint/Challenge concepts, and AI-era findability tooling to the ski/outdoor industry.
|
||||
- Evidence: `C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md`; JSON record `5949`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review before public inclusion.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Added or refined multiple Future Map research/post themes during the period, including AI job displacement and entrepreneurship, AI valuation crash risk, energy-as-currency, China demographics, global demand destruction risk, balance-sheet-supported spending, and AI output overrunning human decision pipelines.
|
||||
- Evidence: JSON records `5937`, `5939`, `5944`, `5945`, `5947`, `5952`, `5955`, `5956`, `5957`, `5961`, `5965`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## PROFESSIONAL CHRONICLE / THE LIGHT OF DOG
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Created or refined a private-training-during-boarding workflow that uses wearable/portable recording, speech-to-text, AI summaries, and content links to turn training activity into richer boarding logs and client-facing reports.
|
||||
- Evidence: `C:\projects\LOD\lod-private-training-during-boarding-stay\README.md`; JSON record `5960`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Avoid client names and private dog/boarding details.
|
||||
|
||||
### Proposed Addition
|
||||
- [Question] Should the PID mention that the AI dog-training / "interpret dog" concept is currently exploratory and possibly being deprioritized in favor of more immediate LOD operational systems?
|
||||
- Evidence: June 8 transcript includes doubts about monetization and timing for an AI-based trainer / dog interpretation concept.
|
||||
- Confidence: Medium.
|
||||
- Privacy: Safe, but should only be included if you want this nuance public.
|
||||
|
||||
## ADDITIONAL SKILLS AND KEYWORDS / SYSTEMS-TECHNOLOGY
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Recent hands-on tools and systems include Hugo/static publishing, semantic discovery files (`ai-index.json`, `llms.txt`, `agents.md`, `skills.md`), `.well-known` agent/security files, reCAPTCHA, Postmark telemetry, Listmonk exports, Git/Gitea SSH deployment, WSL scripts, local VM routing, and publication sanitization workflows.
|
||||
- Evidence: iNDX website task notes; publication receipts; email-campaigns task notes; June 8 transcript.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe when generalized.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Recent AI/workflow skill work includes PID initial creation, PID update maintenance, ratchet-based skill frameworks, run receipts, source authorization gates, and review-first publishing processes.
|
||||
- Evidence: `C:\projects\indx\portable-identity-document-template-OPEN\CHANGELOG.md`; `C:\projects\productivity\misc-productivity-tools-OPEN\skill-template\ratchet-based-skill-framework.md`; updated skill file.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## POSSIBLE THINGS OTHERS MAY NEED FROM YOU
|
||||
|
||||
- [Inference] Associations and niche industries may need help converting AI interest into practical innovation programs, problem surveys, sprint/challenge formats, and shared knowledge libraries.
|
||||
- [Inference] Consumer/outdoor brands may need help becoming AI-findable through structured content, semantic discovery files, GEO/AEO frameworks, and AI-readable websites.
|
||||
- [Inference] Small businesses may need help building low-cost automation workflows using existing tools, scripts, AI-assisted development, and telemetry.
|
||||
- [Inference] Operators building personal AI systems may need frameworks for memory, event logs, local-first architecture, privacy, and PID-style identity layers.
|
||||
- [Inference] Communities trying to avoid platform lock-in may need decentralized identity, trust, freshness, and matching infrastructure.
|
||||
|
||||
## POSSIBLE PEOPLE OR OPPORTUNITIES YOU MAY NEED
|
||||
|
||||
- [Inference] A technical development partner for PaddleNet/NetworkSIG secure ingestion, matching, telemetry, and local-agent orchestration.
|
||||
- [Inference] Association/event operators who can help pilot PTC/SIA-style innovation sprints and challenges.
|
||||
- [Inference] Privacy/security collaborators familiar with encryption, ZK/FHE, identity, and agent-mediated data access.
|
||||
- [Inference] Outdoor industry partners willing to test AI findability, structured content, and brand intelligence frameworks.
|
||||
- [Inference] Early PID users willing to maintain rich PIDs and provide feedback on matching quality, freshness scoring, and agent usability.
|
||||
|
||||
## OPEN QUESTIONS FOR YOU
|
||||
|
||||
- Do you want to publicly describe yourself as open to AI integration / automation consulting, or keep that private while it is still forming?
|
||||
- Should the SIA proposal be included in the PID now, or only after there is a response or public outcome?
|
||||
- How much of the edge data center should be public: high-level capability only, or specific architecture and proof points?
|
||||
- Should the PID mention health/fitness/activity patterns at all, or should those remain entirely private except for broad "outdoor/physical practice" signals?
|
||||
- Do you want "Applied Knowledge & Recommendations" added to your own PID as a section, matching the template direction?
|
||||
- Should the "energy as currency via kWh" work be promoted from Future Map notes into a stronger named framework in the PID?
|
||||
- Do you want the LOD AI dog-training concept included as exploratory, or excluded until it becomes a shipped/active project?
|
||||
|
||||
## SUGGESTED SKILL IMPROVEMENTS BASED ON THIS RUN
|
||||
|
||||
- Add a source-priority heuristic: when the user authorizes very broad roots, inventory metadata first, then prioritize small structured logs, task workflow files, publication receipts, recent Markdown, STT transcripts, and Google Docs with meaningful titles before reading large binaries.
|
||||
- Add a Google Drive stub rule: local `.gdoc`, `.gsheet`, and `.gslides` files are metadata pointers; fetch content through the Drive connector when available.
|
||||
- Add a privacy default: activity trackers often contain health/family/private details, so default to extracting professional/project signals and generalizing personal context unless explicitly approved.
|
||||
- Add a "publication receipt" signal category because your workflow uses receipts as reliable evidence of shipped/sanitized/open-source artifacts.
|
||||
- Add a "strategy proposal / outreach" category with a review flag because proposals can be valuable but may not be public yet.
|
||||
257
review-drafts/PID-what-i-have-projects-review-2026-06-16.md
Normal file
257
review-drafts/PID-what-i-have-projects-review-2026-06-16.md
Normal file
|
|
@ -0,0 +1,257 @@
|
|||
# PID What I Have Review Draft
|
||||
|
||||
Agent response to human when this review draft is complete: This is a draft for your review before anything is added to your Portable Identity Document (PID).
|
||||
|
||||
Please edit freely:
|
||||
- delete anything that should not be included
|
||||
- correct anything inaccurate
|
||||
- add missing context, links, examples, names, or proof
|
||||
- mark private items that should be removed or generalized
|
||||
- strengthen anything that feels too vague or too narrow
|
||||
|
||||
After you edit this draft, ask the agent to continue from your revised file and update the `WHAT I HAVE` section of your PID.
|
||||
|
||||
## Run Scope
|
||||
|
||||
- Review date: June 16, 2026.
|
||||
- Approved source reviewed: `C:\projects`.
|
||||
- PID source reviewed: `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md`.
|
||||
- Prior draft format referenced: `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\PID-update-review-draft-2026-06-16.md`.
|
||||
- Review goal: identify durable assets, scripts, processes, workflows, and project systems under `C:\projects` that could be added to or made more explicit in the PID `WHAT I HAVE` section.
|
||||
- Privacy posture used: standard privacy. I avoided private hostnames, IP addresses, credentials, raw customer/subscriber data, private operational topology, and personal/family/health specifics. Some items are marked `Review` where a public PID should generalize details.
|
||||
- PID update status: awaiting user review. Nothing has been appended to the PID.
|
||||
|
||||
## METADATA, ONTOLOGY AND CONTEXT / WHAT I HAVE
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A Git-backed personal operating system rooted in `C:\projects`, with project repositories, source-controlled Markdown, task workflow logs, publication receipts, skill files, infrastructure inventories, and Google Drive/JSON/NAS/email sources treated as inputs for AI-assisted recall and updates.
|
||||
- Evidence: `C:\projects\1-flows\flows\daily-log.md`; `C:\projects\1-flows\flows\Infra.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Public wording should describe the operating model without listing sensitive data sources in too much detail.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A daily operating and memory-capture workflow that connects task planning, audio logs, project changelogs, CRM/JSON records, calendar review, Git updates, media processing, backups, and AI-assisted prompts into one recurring review loop.
|
||||
- Evidence: `C:\projects\1-flows\flows\daily-log.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Keep specific personal, family, health, and sensitive operational details out of the public PID.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] An infrastructure review flow for keeping edge compute, hardware, software, VMs, domains/routing, cron jobs, backups, telemetry, and project references synchronized as work changes.
|
||||
- Evidence: `C:\projects\1-flows\flows\Infra.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Mention the capability, not private routing details.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A reusable spec-driven product development operating system for building software, services, physical products, workflows, and agents from structured Markdown specs, tasks, `srv/` execution code, `data-ops/`, tests, decisions, personas, and system ontology.
|
||||
- Evidence: `C:\projects\productivity\product-dev-os-OPEN\README.md`; `C:\projects\productivity\product-dev-os-OPEN\specs\3_product_development_s\system-ontology-framework\system-ontology-framework.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A concrete AI-native knowledge-structuring architecture that separates human-readable Markdown/HTML from AI-readable chunks, Q&A, CIS/chunk-intelligence signatures, control-plane metadata, discovery files, versioning, policy overlays, and future vector/graph enrichment.
|
||||
- Evidence: `C:\projects\productivity\ai-knowledge-structure-OPEN\README.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A structured website builder that converts Markdown content into a fast, static, AI-readable website with Hugo, semantic chunks, Q&A JSON, JSON-LD, `ai-index.json`, `llms.txt`, `agents.md`, `skills.md`, sitemap, robots, and `.well-known` discovery/security files.
|
||||
- Evidence: `C:\projects\productivity\structured-website-builder-OPEN\README.md`; `C:\projects\publication-receipts-to-open\2026-06-09-structured-website-builder-publication-receipt.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Deterministic website-publishing scripts that sync authored content to Hugo, build AI discovery indexes, generate root discovery files, and publish Hugo output while preserving key machine-readable files.
|
||||
- Evidence: `C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\sync_content_to_hugo.py`; `C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\build_ai_index.py`; `C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\build_discovery_files.py`; `C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\publish_hugo_output.py`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A website content-structuring skill stack for authoring, chunking, semantic Q&A generation, AI index/discovery materialization, HTML semantic artifact checks, contact-form deployment, and conversion of the builder to new website projects.
|
||||
- Evidence: `C:\projects\indx\indx-front-website\skills-scripts\author-content-structuring-skill.md`; `C:\projects\indx\indx-front-website\skills-scripts\cis-guided-semantic-chunk-generation-skill.md`; `C:\projects\indx\indx-front-website\skills-scripts\semantic-qa-materialization-skill.md`; `C:\projects\indx\indx-front-website\skills-scripts\html-semantic-artifacts-checker-skill.md`; `C:\projects\indx\indx-front-website\skills-scripts\discovery-files-materialization-skill.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A master SEO/GEO/findability framework for the AI era covering differentiation, trust/authority, digitization, semantic structuring, traditional search submissions, industry ontologies, knowledge graphs, and agentic search optimization.
|
||||
- Evidence: `C:\projects\productivity\seo-geo-OPEN\README.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A repeatable private-to-public publication workflow for sanitizing operational repos into useful public templates, including explicit source/file gates, anonymization maps, leak scans, validation tiers, ratchet artifacts, and publication receipts.
|
||||
- Evidence: `C:\projects\productivity\misc-productivity-tools-OPEN\skill-repo-publication-workflow.md`; `C:\projects\publication-receipts-to-open\2026-06-09-structured-website-builder-publication-receipt.md`; `C:\projects\publication-receipts-to-open\2026-06-11-email-campaigns-prod-app-publication-receipt.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A publication-receipt library documenting sanitized releases and review gates for open-source/project-template work, including structured website builder, edge data center, Postmark/Listmonk operations, and email-campaign tooling.
|
||||
- Evidence: `C:\projects\publication-receipts-to-open`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A multi-brand email campaign operations system using Listmonk and Postmark for LOD, EddieSoehnel.com, and iNDX, including HTML campaigns, welcome emails, open/click tracking, non-open follow-ups, exports, backups, and future segmentation/automation planning.
|
||||
- Evidence: `C:\projects\productivity\email-campaigns-prod-app-OPEN\README.md`; `C:\projects\productivity\email-campaigns-prod-app\tasks-workflows`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Avoid private list sizes, recipients, endpoints, and operational credentials.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Email intelligence scripts for exporting Listmonk data, pulling Postmark telemetry, backing up Listmonk, sending welcome emails, and analyzing LOD/iNDX non-open segments for follow-up campaigns.
|
||||
- Evidence: `C:\projects\productivity\email-campaigns-prod-app\srv\export_lod_listmonk_data.sh`; `C:\projects\productivity\email-campaigns-prod-app\srv\export_indx_listmonk_data.sh`; `C:\projects\productivity\email-campaigns-prod-app\srv\pull_lod_postmark_telemetry_from_workstation.sh`; `C:\projects\productivity\email-campaigns-prod-app\srv\pull_indx_postmark_telemetry_from_workstation.sh`; `C:\projects\productivity\email-campaigns-prod-app\srv\analyze_lod_nonopens.py`; `C:\projects\productivity\email-campaigns-prod-app\srv\analyze_indx_nonopens.py`; `C:\projects\productivity\email-campaigns-prod-app\srv\send_welcome.py`; `C:\projects\productivity\email-campaigns-prod-app\srv\backup-listmonk.sh`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Public PID can name the workflow but not private infrastructure values.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A local-first edge data center documentation stack covering hardware tiers, VM strategy, networking, security practices, backup/disaster recovery, monitoring, power resilience, and solar-supported infrastructure.
|
||||
- Evidence: `C:\projects\infra\edge-data-center-main-OPEN\README.md`; `C:\projects\infra\edge-data-center-main\README.md`; `C:\projects\infra\edge-data-center-main-OPEN\PUBLICATION_WORKFLOW.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Keep public wording at architecture/capability level.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A structured hardware and software inventory for the edge environment, with repos for machines, routers, UPS/power systems, NAS devices, Proxmox/Ubuntu VM software, Caddy routing, Gitea, ops monitoring, email campaign VM, and fleet/software inventory scans.
|
||||
- Evidence: `C:\projects\infra\hardware`; `C:\projects\infra\software`; `C:\projects\infra\software\ops-monitor\README.md`; `C:\projects\infra\software\vm-software-inventory-scan\README.md`; `C:\projects\infra\software\caddy-router\README.md`; `C:\projects\infra\software\gitea-prod-app\README.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Generalize names, topology, and endpoints in public PID.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A leak-scan/security-publication process for public infrastructure templates, including PowerShell leak-scan scripts, sanitization maps, `.gitignore` guardrails, and human-review gates before public publication.
|
||||
- Evidence: `C:\projects\infra\edge-data-center-main-OPEN\scripts\leak-scan.ps1`; `C:\projects\infra\edge-data-center-main-OPEN\sanitization-map.md`; `C:\projects\infra\edge-data-center-main-OPEN\PUBLICATION_WORKFLOW.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A PID template and PID maintenance skill system, including initial-creation and update-maintenance skills, source-authorization rules, review drafts, run receipts, and a maturity model for evolving PIDs into stronger AI-readable identity layers.
|
||||
- Evidence: `C:\projects\indx\portable-identity-document-template-OPEN\README.md`; `C:\projects\indx\portable-identity-document-template-OPEN\PID-template.md`; `C:\projects\indx\portable-identity-document-template-OPEN\PID-maturity-model-roadmap.md`; `C:\projects\indx\portable-identity-document-template-OPEN\skills\PID-initial-creation-skill.md`; `C:\projects\indx\portable-identity-document-template-OPEN\skills\PID-update-maintenance-skill.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A working NetworkSIG/PaddleNet business and system strategy for using Portable Identity Documents as structured inputs for matching, trust, freshness, permissions, telemetry, local-agent processing, and future agent-to-agent networking.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-business\specs\1_strategy_s\nsig-vision-strategy.md`; `C:\projects\paddlenet\paddlenet-app\paddlenet-nsig\paddlenet-nsig-pid-ingestion`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A PaddleNet telemetry-learning concept where agents report anonymized session/match telemetry so the network can learn which PID sections, metadata fields, trust signals, match categories, and human feedback patterns create real value.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-app\paddlenet-nsig\paddlenet-nsig-pid-ingestion\3_product_development_s\gate access by requiring telemetry upload.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Public PID should describe the anonymized learning loop, not any live user data.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A PaddleNet/iNDX front-website publishing implementation that uses the structured website builder pattern for content, semantic artifacts, discovery files, contact forms, production launch notes, and ongoing task workflows.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-app\paddlenet-front-website\README.md`; `C:\projects\paddlenet\paddlenet-app\paddlenet-front-website\UPDATES.md`; `C:\projects\paddlenet\paddlenet-app\paddlenet-front-website\tasks-workflows`; `C:\projects\indx\indx-front-website\tasks-workflows`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A PTC/COLAB innovation sprint project space for converting outdoor/association problems into structured challenge work, student/technologist collaboration, and AI-era innovation programming.
|
||||
- Evidence: `C:\projects\paddlenet\paddlenet-colabSIG\ptc-colab-2026-innovation-sprint\README.md`; `C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md`.
|
||||
- Confidence: Medium.
|
||||
- Privacy: Review. Some proposal/outreach material may be pre-public.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A Future Map research workspace for AI, job unbundling, business ownership, public lands, geopolitics, social contracts, consumer behavior, infrastructure sovereignty, and emerging business-model shifts.
|
||||
- Evidence: `C:\projects\future-map\future-map\notes.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe if summarized at theme level.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A Light of Dog AI operations/process layer, including a private-training-during-boarding workflow that uses portable recording, speech-to-text, AI summarization, and linked content to produce richer boarding logs/client reports.
|
||||
- Evidence: `C:\projects\LOD\lod-private-training-during-boarding-stay\README.md`; `C:\projects\LOD\lod-ai-os`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Avoid client/dog-specific details in public PID.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] LOD operational scripts and app maintenance utilities, including payment counter reseeding, file path migration, customer data repair, API app work, and AI OS/spec structure.
|
||||
- Evidence: `C:\projects\LOD\lod-api\scripts\reseed_payment_counter.py`; `C:\projects\LOD\lod-api\scripts\reseed_all_counters.py`; `C:\projects\LOD\lod-api\scripts\migrate_file_paths.py`; `C:\projects\LOD\lod-api\scripts\fix_all_customers.py`; `C:\projects\LOD\lod-ai-os\specs`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Keep private app internals generalized.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A miscellaneous skill and productivity tool library with reusable prompt/workflow skills for publication, product analysis, brainstorming, bias avoidance, autonomous large-build management, database search beyond Google, Google Docs Markdown conversion with images, Garmin FIT extraction, and Git/Gitea release processes.
|
||||
- Evidence: `C:\projects\productivity\misc-productivity-tools-OPEN`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A ratchet-based skill framework and skill-template repo for turning recurring agent mistakes, workflow lessons, validation gaps, and review patterns into durable skill instructions, checklists, fixtures, and anti-patterns.
|
||||
- Evidence: `C:\projects\productivity\misc-productivity-tools-OPEN\skill-template\ratchet-based-skill-framework.md`; `C:\projects\productivity\misc-productivity-tools-OPEN\skill-template\README.md`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A Google Docs Markdown conversion workflow with image extraction support, useful for moving cloud-authored long-form documents into Git/Markdown workflows while preserving media.
|
||||
- Evidence: `C:\projects\productivity\misc-productivity-tools-OPEN\google-doc-md-conversion-with-images\google-doc-md-conversion-skill.md`; `C:\projects\productivity\misc-productivity-tools-OPEN\google-doc-md-conversion-with-images\extract_md_images.py`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A small external-platform-post publishing process that exports tagged JSON hub records into Word/document output for website publication.
|
||||
- Evidence: `C:\projects\productivity\external-platforms-posts-publish\README.md`; `C:\projects\productivity\external-platforms-posts-publish\srv\auto_fix_json_and_export_external_posts.py`.
|
||||
- Confidence: High.
|
||||
- Privacy: Review. Public PID should describe the process without private file paths or unpublished content details.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A CRM/contact-list utility repo with scripts for finding and working with contact data.
|
||||
- Evidence: `C:\projects\productivity\crm-contacts-list\README.md`; `C:\projects\productivity\crm-contacts-list\srv\find.py`.
|
||||
- Confidence: Medium.
|
||||
- Privacy: Review. Do not expose private contacts or CRM contents.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] A Google Analytics workspace and analytics-oriented project area for measuring web traffic and campaign performance.
|
||||
- Evidence: `C:\projects\productivity\google-analytics\README.md`.
|
||||
- Confidence: Medium.
|
||||
- Privacy: Safe if generalized.
|
||||
|
||||
### Proposed Addition
|
||||
- [Fact] Local working copies of advanced agent/memory/reference stacks, including GBrain, GStack, and OpenProse, used as research material for agent memory, skill ecosystems, AI-assisted development roles, responsibility runtimes, and Markdown contracts for agent execution.
|
||||
- Evidence: `C:\projects\repos\gbrain\README.md`; `C:\projects\repos\gstack\README.md`; `C:\projects\repos\prose\README.md`.
|
||||
- Confidence: High that the working copies exist; Medium on how strongly to claim ownership.
|
||||
- Privacy: Safe if phrased as "local reference/evaluation repos" rather than owned inventions.
|
||||
|
||||
### Proposed Addition
|
||||
- [Inference] A practical advantage worth making explicit: you do not only have ideas about AI-native systems; you have a working pattern of turning them into repos, skills, deterministic scripts, public templates, private ops docs, receipts, and repeatable workflows.
|
||||
- Evidence: Cross-cutting pattern across `C:\projects\productivity`, `C:\projects\indx`, `C:\projects\infra`, `C:\projects\paddlenet`, `C:\projects\publication-receipts-to-open`, and `C:\projects\1-flows`.
|
||||
- Confidence: High.
|
||||
- Privacy: Safe.
|
||||
|
||||
## POSSIBLE GROUPING / MERGE NOTES
|
||||
|
||||
- The existing PID already says you have "many more projects, skills, workflows, tools and processes." This review suggests replacing or expanding that broad line with specific groups:
|
||||
- AI-readable identity and PID systems
|
||||
- AI-era findability and structured website publishing
|
||||
- product-development OS and system ontology frameworks
|
||||
- local-first edge infrastructure and ops inventory
|
||||
- email/list/telemetry automation
|
||||
- private-to-public publication and sanitization workflows
|
||||
- daily operating system and memory-capture flows
|
||||
- LOD, PaddleNet/iNDX, Future Map, and PTC/SIA applied project spaces
|
||||
- reusable skill/tool library
|
||||
|
||||
- The PID `WHAT I HAVE` section could add a new subsection called `Operational Assets And Workflows` or `Working Systems And Reusable Assets` so these do not get lost in the strategy sections.
|
||||
|
||||
- For public readability, avoid turning `WHAT I HAVE` into a raw repo catalog. The strongest pattern is: "I have a working system for X, backed by repos/scripts/workflows Y."
|
||||
|
||||
## OPEN QUESTIONS FOR YOU
|
||||
|
||||
- Should the public PID describe `C:\projects` as your "personal operating system," "working project graph," "AI-operable project workspace," or something else?
|
||||
- Do you want local reference repos like GBrain/GStack/OpenProse listed as things you are studying/evaluating, or should they be omitted from `WHAT I HAVE` because they are not your authored assets?
|
||||
- How specific should the PID be about edge infrastructure: high-level capability only, or proof points like solar, UPS, recycled hardware, VM inventory, Caddy/Gitea/ops monitor?
|
||||
- Should email campaign tooling be framed as an iNDX/LOD internal capability, an open-source template, or both?
|
||||
- Do you want the daily operating system and memory-capture flow included publicly, or should it remain private context that only informs future PID updates?
|
||||
- Should PTC/SIA proposal work be included now, or only after there is a public outcome?
|
||||
- Should LOD operational scripts/processes appear in the PID as "The Light of Dog operational AI systems," or stay out unless they are customer-facing?
|
||||
|
||||
## SUGGESTED PID Wording Candidates
|
||||
|
||||
These are not final edits, just candidate phrasings for the `WHAT I HAVE` section.
|
||||
|
||||
- "A Git-backed personal operating system under `C:\projects` that organizes strategy, specs, workflows, scripts, infrastructure, receipts, and project memory into AI-readable repositories."
|
||||
- "A reusable structured website builder for the AI era that turns Markdown into fast static websites with semantic chunks, Q&A JSON, JSON-LD, `ai-index.json`, `llms.txt`, `agents.md`, `skills.md`, sitemaps, robots, and `.well-known` discovery files."
|
||||
- "A private-to-public publication workflow for converting operational repos into sanitized public templates with explicit source gates, anonymization maps, leak scans, validation tiers, ratchet artifacts, and publication receipts."
|
||||
- "A multi-brand email/list intelligence stack using Listmonk and Postmark, with export, telemetry pull, non-open analysis, welcome-email, and backup scripts."
|
||||
- "A local-first edge compute and resilience stack documented across hardware, software, VM, routing, backup, monitoring, power, and solar-support repos."
|
||||
- "A PID/template/skill system for creating and maintaining review-first, evidence-backed portable identity documents as AI-readable identity layers."
|
||||
- "A NetworkSIG/PaddleNet strategy and prototype direction for using PIDs, local agents, telemetry, trust, freshness, and permission signals to support agent-mediated matching."
|
||||
- "A reusable skill and productivity-tool library that captures repeatable agent workflows, publication processes, product-analysis prompts, bias checks, conversion scripts, and ratchet-based skill design."
|
||||
|
||||
211
skill-receipts/PID-update-run-receipt-2026-06-16.md
Normal file
211
skill-receipts/PID-update-run-receipt-2026-06-16.md
Normal file
|
|
@ -0,0 +1,211 @@
|
|||
# PID Update Run Receipt
|
||||
|
||||
## Skill Run
|
||||
|
||||
- Skill name: pid-update-maintenance
|
||||
- Skill source/path: `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\skills\PID-update-maintenance-skill.md`
|
||||
- Skill version or file timestamp if known: read and patched on June 16, 2026 to strengthen explicit source authorization requirements.
|
||||
- Run date: 2026-06-16
|
||||
- Executor/host: Codex desktop, PowerShell, Google Drive connector.
|
||||
- User request: Run the PID update maintenance skill for the existing PID covering the last 10 days, with approved sources `C:\Users\edsoe\My Drive` and `C:\projects`.
|
||||
|
||||
## Timeframe
|
||||
|
||||
June 6, 2026 through June 16, 2026.
|
||||
|
||||
## PID Source
|
||||
|
||||
`C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md`
|
||||
|
||||
## PID Format And Edit Method
|
||||
|
||||
- Format: Markdown.
|
||||
- Edit method for this run: review draft only. The PID was not modified because the skill requires user review and approval first.
|
||||
|
||||
## Inputs Used
|
||||
|
||||
- Current PID: `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md`
|
||||
- Review draft: `PID-update-review-draft-2026-06-16.md`
|
||||
- Revised review draft: none yet.
|
||||
- User-provided instructions: cover the last 10 days; approved sources are `C:\Users\edsoe\My Drive` and `C:\projects`.
|
||||
- Privacy boundaries: not explicitly stated in the second source list; standard privacy applied.
|
||||
- Update goals: maintain current PID with recent accomplishments, projects, learnings, proof, needs, offers, and match-context signals.
|
||||
|
||||
## Assumptions Made
|
||||
|
||||
- "Last 10 days" was interpreted as June 6, 2026 through June 16, 2026.
|
||||
- Standard privacy means health, family, client, financial, legal, account, credential, private network, and operational-security details should be excluded, generalized, or presented as review questions.
|
||||
- The PID repo itself is not assumed to be the only source; it was reviewed only because `C:\projects` was explicitly approved and it contained relevant PID work.
|
||||
- Google Drive `.gdoc`, `.gsheet`, and `.gslides` local files are pointer/stub files; relevant content was fetched through the Google Drive connector when feasible.
|
||||
|
||||
## Capabilities Used
|
||||
|
||||
- Filesystem: read approved source roots; created local draft and receipt.
|
||||
- Connectors: Google Drive search with best-effort fetch for selected docs.
|
||||
- Browser/network: none.
|
||||
- Subagents: none.
|
||||
- Document/PDF/spreadsheet tools: no dedicated PDF rendering; PDF titles and selected Drive-fetched content were used where available, but most PDFs were not deeply extracted.
|
||||
|
||||
## Tool Calls Or Commands Executed
|
||||
|
||||
- Read skill file.
|
||||
- Read current PID.
|
||||
- Listed PID repo contents.
|
||||
- Extracted PID headings.
|
||||
- Patched PID skill to require explicit source listings and not assume PID repo as source.
|
||||
- Inventoried recently modified files under `C:\Users\edsoe\My Drive`.
|
||||
- Inventoried recently modified files and Git repositories under `C:\projects`.
|
||||
- Read recent JSON activity records under `C:\Users\edsoe\My Drive\Personal Organization\JSON_Database\hrecords`.
|
||||
- Read recent STT transcript `C:\Users\edsoe\My Drive\Personal Organization\Logs Calls Meeting STT\2026_06_08_06_43_23_1.txt`.
|
||||
- Read selected project files and publication receipts in `C:\projects`.
|
||||
- Queried Git logs across repositories under `C:\projects`.
|
||||
- Used Google Drive connector searches for selected documents including Outdoor Brand Innovation Intelligence Report, PTC Innovation Directive, ALX PaiOS, Energy As Currency Via kWh, and Decentralized AI-Native Professional Networking.
|
||||
|
||||
## External State Changed
|
||||
|
||||
- Files created:
|
||||
- `PID-update-review-draft-2026-06-16.md` in current workspace.
|
||||
- `PID-update-run-receipt-2026-06-16.md` in current workspace.
|
||||
- Files modified:
|
||||
- `C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\skills\PID-update-maintenance-skill.md` was patched earlier in response to user correction.
|
||||
- Cloud documents modified: none.
|
||||
- PID changed: no.
|
||||
- Nothing changed without explicit user approval: PID was not modified. Skill patch was made after user explicitly requested it and approved escalation.
|
||||
|
||||
## Approved Sources Reviewed
|
||||
|
||||
- `C:\Users\edsoe\My Drive`
|
||||
- Recent file metadata.
|
||||
- JSON activity records.
|
||||
- One STT text transcript.
|
||||
- Selected Google Drive docs through connector.
|
||||
- `C:\projects`
|
||||
- Recent file metadata.
|
||||
- Selected Markdown task/workflow files.
|
||||
- Selected publication receipts.
|
||||
- Selected project strategy files.
|
||||
- Git repository list and recent logs.
|
||||
- Current PID file.
|
||||
|
||||
## Sources Skipped Or Unavailable
|
||||
|
||||
- Most `.gdoc`, `.gsheet`, and `.gslides` local stubs could not be read directly as content from disk; selected docs were fetched through Google Drive by title.
|
||||
- Most PDFs were not deeply extracted due to time and relevance triage. Their filenames influenced source inventory; selected Drive-fetched PDF content appeared in connector results where available.
|
||||
- Email/Gmail, calendar, browser history, NAS media, cloud backup exports, and CRM connectors were not separately reviewed because only local roots were explicitly listed, and no separate account/label/query scopes were provided.
|
||||
- FIT files were inventoried but not parsed.
|
||||
|
||||
## Sources Not Authorized Or Intentionally Excluded
|
||||
|
||||
- Any source outside `C:\Users\edsoe\My Drive` and `C:\projects`.
|
||||
- Private raw recipient lists, credentials, hostnames/IPs, account details, private health/family/legal/financial details were not included as proposed public PID text.
|
||||
|
||||
## Draft Created
|
||||
|
||||
`PID-update-review-draft-2026-06-16.md`
|
||||
|
||||
## User Review Status
|
||||
|
||||
Awaiting user review. User has not approved draft for PID insertion.
|
||||
|
||||
## PID Update Status
|
||||
|
||||
PID unchanged. Awaiting review and approval.
|
||||
|
||||
## Outputs Produced
|
||||
|
||||
- Review draft: `PID-update-review-draft-2026-06-16.md`
|
||||
- Source map: source/evidence notes are embedded in the review draft rather than created as a separate file.
|
||||
- Open questions: embedded in the review draft.
|
||||
- Updated PID or copy-ready update: not produced yet.
|
||||
- Run receipt: `PID-update-run-receipt-2026-06-16.md`
|
||||
|
||||
## Validation Results
|
||||
|
||||
- Current PID was read.
|
||||
- PID structure was used rather than generic fallback.
|
||||
- Review draft was created before any PID update.
|
||||
- Every proposed addition is mapped to a PID section.
|
||||
- Facts are labeled as facts and include evidence.
|
||||
- Inferences are labeled as inferences.
|
||||
- Questions are labeled as questions.
|
||||
- Standard privacy was applied.
|
||||
- PID was not modified before user review.
|
||||
- Run receipt was created.
|
||||
|
||||
## Privacy Decisions
|
||||
|
||||
- Health/activity tracker details were mined only for professional/project signals and were not proposed as public health detail.
|
||||
- Family, client, dog boarding, financial, legal, and private account details were either omitted or generalized.
|
||||
- Edge infrastructure details were summarized at capability level, with a review note to avoid public exposure of hostnames, keys, IPs, and exact security posture.
|
||||
- Email campaign details were summarized as workflow/proof of work, not recipient-level data.
|
||||
|
||||
## Notable Inferences
|
||||
|
||||
- A technical development partner may help accelerate NetworkSIG/PaddleNet.
|
||||
- The user may be moving toward an AI integration / automation specialist positioning.
|
||||
- Industry associations and niche communities may be strong match opportunities for innovation sprint/challenge formats.
|
||||
- Publication receipts are high-quality proof artifacts for shipped/open-source work.
|
||||
|
||||
## Unsupported Or Low-Confidence Items Removed, Downgraded, Or Turned Into Questions
|
||||
|
||||
- AI dog-training / interpret-dog work was turned into a review question because the transcript suggested uncertainty and possible deprioritization.
|
||||
- SIA proposal inclusion was marked for review because proposal/outreach status may be private or premature.
|
||||
- Health/fitness signals were excluded from proposed public updates except broad outdoor/physical-practice implications.
|
||||
- Exact infrastructure/security details were generalized.
|
||||
|
||||
## Failures Or Gaps Found
|
||||
|
||||
- Original skill language allowed ambiguity that led the agent to initially assume the PID repo might be the primary source. This was corrected before the source scan.
|
||||
- Very broad source roots create large review surfaces; metadata-first triage was necessary.
|
||||
- Local Google Drive stubs do not expose document content directly.
|
||||
- Calendar/email/source connectors were not fully scoped by user, so they were not separately reviewed.
|
||||
|
||||
## Fixes Applied
|
||||
|
||||
- Patched `PID-update-maintenance-skill.md` to require explicit source locations/scopes and warn not to assume the PID repo or PID folder is an approved source.
|
||||
- Used Google Drive connector for selected documents where local stubs were insufficient.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Should the PID publicly mention AI integration / automation consulting availability?
|
||||
- Should the SIA proposal be included now?
|
||||
- How specific should the public PID be about edge-compute infrastructure?
|
||||
- Should health/fitness/activity signals remain entirely private?
|
||||
- Should "Applied Knowledge & Recommendations" be added to Eddie's own PID?
|
||||
- Should "Energy as Currency via kWh" become a named framework in the PID?
|
||||
- Should LOD AI dog-training exploration be included or withheld?
|
||||
|
||||
## Ratchet Lessons
|
||||
|
||||
- Future runs should ask for exact source locations and not assume the PID repo as an activity source.
|
||||
- Future runs should prioritize activity logs, receipts, task workflow docs, and Google Docs with relevant titles when broad roots are authorized.
|
||||
- Future runs should treat Drive stubs as pointers and use Drive connectors where available.
|
||||
- Future runs should treat publication receipts as proof-of-work evidence.
|
||||
|
||||
## Ratchet Artifacts Added Or Suggested
|
||||
|
||||
- Added directly to skill: explicit source listing requirement and validation rule against PID-folder source assumptions.
|
||||
- Suggested in draft:
|
||||
- source-priority heuristic
|
||||
- Google Drive stub rule
|
||||
- standard privacy default for activity trackers
|
||||
- publication receipt signal category
|
||||
- strategy proposal/outreach review flag
|
||||
|
||||
## Unresolved Risks
|
||||
|
||||
- Broad roots may contain sensitive material that was not deeply reviewed but could be accidentally surfaced in future runs without privacy rules.
|
||||
- Some Google Docs and PDFs were not fully read.
|
||||
- Some relevant email/calendar evidence may be missing because account/label/calendar scopes were not explicitly provided.
|
||||
- Draft may overrepresent highly visible recent project clusters and underrepresent quieter relationship or calendar signals.
|
||||
|
||||
## Resume / Audit Notes
|
||||
|
||||
- How a future agent can continue: read `PID-update-review-draft-2026-06-16.md`, apply user edits, then append approved items into the matching PID sections.
|
||||
- What should be reviewed first: open questions, privacy notes, SIA proposal inclusion, infrastructure specificity, and whether AI integration consulting positioning should be public.
|
||||
|
||||
## Recommended Next Steps
|
||||
|
||||
- User reviews and edits the draft.
|
||||
- After approval, append approved additions to the existing PID sections rather than rewriting the whole PID.
|
||||
- If user agrees, copy the draft and receipt into the PID repo / `skill-receipts` folder for durable storage.
|
||||
212
skills/PID-update-maintenance-skill-user-variables.md
Normal file
212
skills/PID-update-maintenance-skill-user-variables.md
Normal file
|
|
@ -0,0 +1,212 @@
|
|||
# PID Update Maintenance Skill User Variables
|
||||
|
||||
## Purpose
|
||||
|
||||
This is the user-owned companion configuration file for `PID-update-maintenance-skill.md`.
|
||||
|
||||
Keep user-specific variables here so the main skill can improve over time without overwriting a user's local paths, source permissions, privacy rules, output preferences, or workflow adjustments.
|
||||
|
||||
Agents using the main PID update maintenance skill should read this file first when it exists beside the main skill. Treat this file as user-controlled configuration and preference context, not as a replacement for the main workflow or validation gates.
|
||||
|
||||
## How To Use
|
||||
|
||||
1. Copy this file beside `PID-update-maintenance-skill.md`.
|
||||
2. Fill in only the fields that apply.
|
||||
3. Keep private values in your own local copy when needed.
|
||||
4. When the main skill is updated, preserve this file unless the user explicitly asks to replace it.
|
||||
5. If a field conflicts with the main skill, follow the stricter privacy/review rule unless the user gives explicit approval.
|
||||
|
||||
## Current PID
|
||||
|
||||
- PID location or link: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md
|
||||
- PID format: Markdown / Google Doc / Word / OneDrive / PDF / website / repo / other Markdown
|
||||
- Canonical source of truth: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md
|
||||
- Direct editing allowed: yes / no / ask each time no
|
||||
- Preferred update method: direct edit / copy-ready Markdown / review draft only - review draft only
|
||||
|
||||
## Default Timeframe
|
||||
|
||||
- Default review window: last 7 days
|
||||
- Alternative recurring window:
|
||||
- Date/timezone preference:
|
||||
|
||||
## Output Locations
|
||||
|
||||
- Review draft folder: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\review-drafts
|
||||
- Review draft filename pattern: `PID-update-review-draft-[YYYY-MM-DD].md`
|
||||
- Source map folder:
|
||||
- Open questions folder: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\skill-receipts
|
||||
- Run receipt folder: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\skill-receipts
|
||||
- Run receipt filename pattern: `PID-update-run-receipt-[YYYY-MM-DD].md`
|
||||
|
||||
## Approved Data Sources
|
||||
|
||||
List every source the agent may review. Do not rely on the main skill to infer these.
|
||||
|
||||
### Local PC Folders
|
||||
|
||||
- "C:\Users\edsoe\My Drive"
|
||||
- "C:\projects"
|
||||
|
||||
### Cloud File Locations Or Connectors
|
||||
|
||||
-
|
||||
|
||||
### Git Repositories
|
||||
|
||||
-
|
||||
|
||||
### Email Accounts, Labels, Or Queries
|
||||
|
||||
-
|
||||
|
||||
### Calendar Accounts Or Ranges
|
||||
|
||||
-
|
||||
|
||||
### Meeting Transcript Or Recording Export Locations
|
||||
|
||||
-
|
||||
|
||||
### Chat Logs Or Collaboration Tool Exports
|
||||
|
||||
-
|
||||
|
||||
### CRM, Database, CSV, JSON, Or Spreadsheet Exports
|
||||
|
||||
-
|
||||
|
||||
### Browser Bookmarks, Reading Lists, Or History
|
||||
|
||||
- chrome://history/
|
||||
|
||||
### Social, Newsletter, Publishing, Portfolio, Or Website Sources
|
||||
|
||||
- https://indx.earth/community-summaries
|
||||
- https://thelightofdog.com/newsletter/
|
||||
|
||||
### Photos, Screenshots, Design Files, Or Media Metadata
|
||||
|
||||
-
|
||||
|
||||
### Learning Logs, Courses, Books, Papers, Or Saved Articles
|
||||
|
||||
-
|
||||
|
||||
### Financial, Sales, Support, Product, Or Analytics Exports
|
||||
|
||||
-
|
||||
|
||||
### Other Sources
|
||||
|
||||
-
|
||||
|
||||
## Sources Not Authorized
|
||||
|
||||
List paths, accounts, connectors, labels, folders, or source types that must not be scanned.
|
||||
|
||||
-
|
||||
|
||||
## Privacy Boundaries
|
||||
|
||||
### Never Include
|
||||
|
||||
- santization map here: C:\projects\productivity\misc-productivity-tools-OPEN\skill-repo-publication-workflow.md
|
||||
|
||||
### Summarize But Do Not Name
|
||||
|
||||
-
|
||||
|
||||
### Ask Before Including
|
||||
|
||||
-
|
||||
|
||||
### Safe To Include
|
||||
|
||||
-
|
||||
|
||||
## Update Goals
|
||||
|
||||
Based on questions below, best matches right now are anyone that can help me build indx.earth (whether that is development or more importantly, customers and users for it in the outdoor industry, but moreso building momentum I already have in paddling segment) and its matching components, especially networkSIG - the networking app for the AI era
|
||||
|
||||
- What people, opportunities, markets, or matches matter right now?
|
||||
- What current needs should be especially visible?
|
||||
- What current offers or assets should be especially visible?
|
||||
- What should AI systems not misunderstand about the user?
|
||||
|
||||
## Section Preferences
|
||||
|
||||
Use this area to tune how the main skill maps findings into the user's PID.
|
||||
|
||||
- Sections to prioritize:
|
||||
- Sections to keep brief:
|
||||
- Sections that should usually remain private:
|
||||
- Sections that should receive detailed evidence:
|
||||
- Preferred section names if different from the template:
|
||||
- Custom PID sections to preserve:
|
||||
|
||||
The section "What I have" is where I want to contoinually update. The rest of the PID is much more static, except for my Insight Hub/JSON database where I publish additional signals almost daily. That can be weekly signals publishing.
|
||||
|
||||
## Voice And Style Preferences
|
||||
|
||||
- Preferred tone:
|
||||
- Avoid these phrases or framings:
|
||||
- Use first person / third person:
|
||||
- Detail level:
|
||||
- Public-facing wording preference:
|
||||
|
||||
## Review And Approval Rules
|
||||
|
||||
- Always create review draft before PID update: yes
|
||||
- Require user approval before direct PID edit: yes
|
||||
- Require separate approval before public publication: yes
|
||||
- Require separate approval before including inferred needs: yes / no / ask
|
||||
- Require separate approval before including inferred offers: yes / no / ask
|
||||
- Require separate approval before including personal, health, family, financial, legal, client, or private operational details: yes
|
||||
|
||||
## Skill Adjustments For This User
|
||||
|
||||
Use this section for user-specific adjustments to the main skill. These are intended to tune behavior without editing the main skill.
|
||||
|
||||
Examples:
|
||||
- Prefer detailed `WHAT I HAVE` extraction over weekly activity summaries.
|
||||
- Treat publication receipts as high-confidence evidence of shipped work.
|
||||
- Treat proposals and outreach as review-only until user confirms public status.
|
||||
- Generalize edge infrastructure and private operational details.
|
||||
|
||||
User-specific adjustments:
|
||||
|
||||
-
|
||||
|
||||
## Source Priority Rules
|
||||
|
||||
Optional guidance for scanning broad source roots.
|
||||
|
||||
- Prioritize:
|
||||
- Deprioritize:
|
||||
- Skip generated/cache folders:
|
||||
- Treat these folders as public-safe:
|
||||
- Treat these folders as private/review-only:
|
||||
|
||||
## Evidence Rules
|
||||
|
||||
- Evidence detail level:
|
||||
- Acceptable evidence types:
|
||||
- Require source paths in review draft: yes / no
|
||||
- Require confidence labels: yes
|
||||
- Require privacy labels: yes
|
||||
- Treat unsupported inferences as questions: yes
|
||||
|
||||
## Run Receipt Preferences
|
||||
|
||||
- Always create run receipt: yes / no / serious runs only
|
||||
- Receipt folder: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\skill-receipts
|
||||
- Include command/tool log: yes / no
|
||||
- Include skipped sources: yes
|
||||
- Include privacy decisions: yes
|
||||
- Include ratchet lessons: yes
|
||||
|
||||
## Ratchet / Future Skill Improvement Notes
|
||||
|
||||
Use this section to store recurring lessons that should improve future runs.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user