Share to Parable

1. The button

The simplest integration is a single anchor tag. Drop it anywhere users would expect a "send to my notes" action — next to a bookmark icon, inside a share sheet, in an editor toolbar. Live preview:

<!-- Share to Parable / Create note in Parable -->
<a class="parable-button"
   href="https://parable.social/share"
   target="_blank" rel="noopener">
  <span class="parable-button__mark" aria-hidden="true"><svg viewBox="0 0 512 512" width="14" height="14" fill="currentColor" aria-hidden="true"><path d="M 181 103 L 190 99 L 200 97 L 210 98 L 221 102 L 231 107 L 241 114 L 251 123 L 259 134 L 267 145 L 274 157 L 280 170 L 285 183 L 289 196 L 291 209 L 293 222 L 294 235 L 294 247 L 294 259 L 293 271 L 291 283 L 288 294 L 285 305 L 409 389 L 414 374 L 415 356 L 412 336 L 406 315 L 396 292 L 383 269 L 367 247 L 348 225 L 327 205 L 305 187 L 282 172 L 258 159 L 234 150 L 211 144 L 189 142 L 169 143 L 151 148 L 135 156 L 122 166 L 111 179 L 104 194 L 99 210 L 98 215 Z"/><path d="M 408 392 L 399 403 L 387 411 L 373 414 L 356 414 L 338 410 L 318 402 L 298 390 L 278 375 L 258 357 L 239 337 L 221 315 L 205 292 L 191 268 L 180 244 L 171 221 L 164 198 L 161 177 L 160 158 L 161 141 L 164 127 L 170 115 L 177 107 L 98 219 L 97 237 L 100 255 L 104 273 L 111 290 L 120 306 L 130 321 L 141 334 L 153 345 L 165 354 L 177 361 L 190 366 L 202 369 L 214 370 L 224 369 L 235 366 L 244 362 L 252 356 L 260 349 L 267 341 L 272 333 L 278 323 L 282 313 L 283 310 Z"/></svg></span>
  <span class="parable-button__label">Share to Parable</span>
</a>

<style>
  .parable-button {
    display: inline-flex; align-items: center; gap: 8px;
    padding: 8px 14px; border-radius: 9999px;
    background: #0b0b0c; color: #f3e9c7;
    font: 600 14px/1 system-ui, sans-serif;
    text-decoration: none; border: 1px solid #d4a843;
    transition: background .15s ease, transform .15s ease;
  }
  .parable-button:hover { background: #15151a; transform: translateY(-1px); }
  .parable-button__mark {
    display: inline-flex; align-items: center; justify-content: center;
    width: 20px; height: 20px; border-radius: 9999px;
    background: #d4a843; color: #0b0b0c;
  }
</style>

2. Entry URL

The stable, public integrator URL is:

This is a content-free entry point. Do not append user content, attachment names, access tokens, identifiers, or third-party metadata in either the query string or the fragment. Content-bearing URL parameters and fragments are rejected, then the user is taken to a blank compose surface.

An integration may open the notebook, but it cannot pre-fill a note. The user selects, pastes, or attaches material locally and explicitly chooses whether to save it.

3. Content hand-off

There is intentionally no public URL data shape for note contents. A third-party integration must keep its user content in its own trusted context until the user manually transfers it into Parable. This prevents accidental disclosure through browser history, referrers, logs, analytics, screenshots, and link sharing.

For automated or server-to-server provenance, use a separately designed, authenticated protocol rather than treating a browser URL as a transport channel.

4. JS helper

If you'd rather wire it from JavaScript than emit a static link:

function openParableNotebook() {
  // Content stays in the calling product until the user chooses what to
  // paste or attach in Parable. Do not add content, tokens, or identifiers.
  window.open('https://parable.social/share', '_blank', 'noopener');
}

openParableNotebook();

CLI / shell:

# Open the content-free compose surface in a browser
xdg-open "https://parable.social/share"

5. UX & auth behaviour

• Signed in already? Parable opens the /notes editor in a new tab. The user adds content locally, reviews it, and taps Save.
• Not signed in? Parable bounces to the welcome flow and then opens a blank compose surface. It does not retain an external integration's content while identity setup occurs.
• Locked identity? The inline unlock prompt (passkey or passphrase) appears before saving; the compose surface remains content-free until the user adds material.
• No silent commits. The user always reviews their material and explicitly chooses to save. An integration cannot cause a write to the user's chain.

6. Privacy contract

The entry URL is not a content hand-off or an API call. Concretely:

• The public URL carries no user content. Content-bearing query parameters and fragments are rejected instead of being copied into the notebook.
• On save, the note content, title, tags, and attachment metadata are encrypted with AES-256-GCM under a per-note key sealed to the user's ML-KEM-768 identity, then signed with ML-DSA-65 and committed to their Veritas chain. The originating integration receives no implicit access to the resulting note.
• Do not try to send secrets, access tokens, or third-party PII in the URL. They are not an accepted part of this interface; URLs are routinely exposed to browser history, copied links, logs, and screen recorders.
• For headless, signed integrations (server-to-server provenance, automated note creation, etc.) use the signed-envelope endpoints documented under Developer endpoints instead.

7. Brand & placement

The "Share to Parable" wordmark, the gold dot, and the parable.social domain are the only required brand surfaces. The button above is a reference implementation — feel free to restyle it to fit your product, with two constraints:

• Keep the word Parable in the label (e.g. "Share to Parable", "Save in Parable", "Open in Parable").
• Link to parable.social or a subpath of it; do not deep-link past /share or /notes.

That's the whole contract. If you ship something we should know about, say hi at parable.social.

See also: Parable architecture & identity docs · Signed-envelope endpoints · Developer dashboard.

PATENT PENDING · Ma'atara Protocol