LogicSRC standards surface
++ One Markdown file that says who you are and where you are, for people and agents alike. + Meta tags for a profile: served by any site, linked from any platform, readable by + anything. +
++ Every platform has a profile page, and every profile page is a dead end. Your Bluesky bio + cannot tell a job board what you write about. Your GitHub page cannot tell a resharing + network which topics you will boost and what that costs. An agent has it worse: a handle on + six networks, an operator somewhere behind it, and nowhere all of that is written down + together. OpenProfile.md is that place. It ties a name to its accounts, its topics, its + terms and, for an agent, the person answerable for it, in a form that survives being + copied between tools. +
++ Status: 0.1. A convention already in use by{" "} + myna and{" "} + agenticjobs, published so others can serve and read + the same file. +
+A person, and the one section an agent adds.
+{EXAMPLE}
+ {AGENT}
+ Every one of them degrades rather than fails.
+| Rule | +What it means | +
|---|---|
| + + {index + 1}. {rule} + + | +{meaning} | +
The file is served, not registered. A reader tries all three.
+| Where | +How | +When | +
|---|---|---|
| + {where} + | +
+ {how}
+ |
+ {when} | +
+ Serve it as text/markdown; charset=utf-8. A reader fetching the
+ well-known location is reading, not saving, so no attachment disposition there.
+
An account is a claim until the page links back.
+
+ A listed account is verified when its platform page carries{" "}
+ rel="openprofile" or{" "}
+ rel="me" back to the file, or when the bio, website
+ field or pinned post contains the file's URL in plain text. A reader shows verified and
+ claimed accounts differently and hides neither, because most accounts are unverified for a
+ while and a claim is still information. An agent that names its operator, and an operator
+ whose file lists the agent under Accounts, are one trust chain: either link alone is a
+ claim, both together are a verification.
+
| + {what} + | +{why} | +
/.well-known/openprofile.md.
+ myna profile write builds one from the accounts myna is logged
+ into and the topics in its settings. myna reshare join{" "}
+ publishes the Reshare section to the myna reshare network, which matches authors and
+ sharers by topic and settles the rate through CoinPay when there is one.
+ /candidates/<slug>/openprofile.md, derived from the
+ candidate's OpenResume.md, and links it from the profile page.
+