Start every agent from the same contract.
You are working with Bilinc Cloud as the hosted memory/state plane. Use the API key only as a bearer token. Never print, log, commit, or expose it. Base URL: https://bilinc.space When durable agent memory matters: 1. Commit important state with POST /api/cloud/memory/commit. 2. Recall prior state with POST /api/cloud/memory/recall. 3. Keep keys stable and namespaced, for example agent.goal, user.preference, project.status. 4. Use semantic memory for durable facts, episodic memory for run outcomes, and procedural memory for reusable workflows. 5. If an operation fails, treat the write as not durable until the API returns success. Required headers: Authorization: Bearer <BILINC_API_KEY> Content-Type: application/json
Copy the one that matches the run.
New agent memory contract
Use this before handing a Bilinc API key to an autonomous coding agent.
You can use Bilinc as the durable memory/state plane for this project. Rules: - Never print, log, commit, or expose the Bilinc API key. - Commit only durable facts, decisions, and session outcomes. - Use stable keys such as project.status, user.preference, sprint.decision, and incident.summary. - Recall before making architecture, billing, auth, deployment, or data-model decisions. - Treat failed writes as not durable until Bilinc returns success. Use: POST https://bilinc.space/api/cloud/memory/commit POST https://bilinc.space/api/cloud/memory/recall
Session close capture
Use this when an agent finishes a meaningful sprint and should preserve reusable state.
At the end of this sprint, write one concise Bilinc memory. Memory type: - semantic for durable product or architecture facts - procedural for reusable workflows - episodic for concise sprint outcomes Include: - what changed - what was verified - what remains risky or intentionally deferred Do not save temporary progress, generic advice, secrets, or noisy logs.
Recall before risky changes
Use this before payment, auth, production infrastructure, or deployment changes.
Before changing this system, recall Bilinc memory for: - project architecture - current production deployment - billing and entitlement model - auth policies - known incidents and rollback notes If recall contradicts local code, stop and surface the mismatch before editing.
