# Symbiotic Second Brain — portable kit 0.4.0-alpha.13

## Start with your own responsibility

1. Download the complete portable ZIP. In an approved ChatGPT Work conversation with file and code tools, attach it. Uploading the kit is not native installation.
2. Say: “Open the ZIP. Read ChatGPT-Startup.md and skills/symbiotic-second-brain/SKILL.md. Create second brain for xyz. Ask me what responsibility xyz should cover, then guide me one step at a time using only information I supply or authorize.”
3. Agree the responsibility, outcome, acceptance checks and save location. Supply a small amount of information you are permitted to share. The kit does not include a preloaded example brain.
4. Inspect the draft. Ask for the saved work JSON and companion generated with the bundled renderer. Open the generated HTML: Work is the default view; Development offers optional practice guidance.
5. Retain a separate learning record and include it in the dashboard only with explicit private consent.
6. Download records and HTML into your approved folder. Generated conversation files can be temporary; this is not automatic Drive storage.
7. Resume in a fresh chat by attaching the kit and saved work, then ask to continue the existing brain, identify draft versus accepted state and regenerate its companion. Add learning separately only if desired.

If uploads or code tools are blocked, do not bypass controls. Discuss your responsibility in an approved chat or follow the demonstration. Do not claim files were saved or a dashboard generated without evidence.

## Native plugin and Claude

The ChatGPT plugin archive contains the same shared skill and renderer. Installation depends on workspace permission. Once installed, invoke the skill; no starter attachment is needed.

The Claude skill archive uses the same source. In your approved Claude account, open Customize > Skills > Add skill > Upload skill; upload the archive and enable it. If the uploader requires ZIP, use a .zip filename for the same archive. Code execution and skill creation must be permitted. Native setup, both views, progress review with refreshed dashboard and fresh-chat recovery have passed in Allan’s ChatGPT and Claude accounts. Verify behavior in your own environment; account/device permissions and actual human learning are not established by those tests.

## Optional progress review

Choose Prepare progress review, then Copy request > paste into your Second Brain chat > review the results. Or type “Review my development and recommend what to practice next” in that chat.

After a consented review, the assistant must save a new report and regenerate the dashboard with that report's findings and recommendations where its tools permit. Open the new artifact; an older HTML page does not update itself. If saving or rendering is unavailable, the assistant must name the missing step. Existing work, baseline and previous reports remain unchanged.

## Print or save PDF

Choose Work only, Development only, or Work and Development, then Print / save PDF. Select Save as PDF in the browser dialog. If a preview blocks printing, download the HTML and open it in your browser. The button cannot verify whether you saved a PDF. Development may contain private observations; choose Work only when sharing work without that material.

If printing is blocked, ask the chat to generate an actual PDF from the saved records for the selected views, keeping private development out of Work-only exports. ChatGPT document-generated exports have been tested; actual browser-generated output and Claude-specific PDF export remain separate checks. Download and inspect the file before relying on it.

## Local rendering

With Python 3, run the bundled scripts/render_dashboard.py against your authorized saved work.json. Include a learning file, baseline or report only under the appropriate private display consent. The renderer's --help explains the supported arguments. Use its actual returned output filename. The companion is a read-only projection, not the source of truth.

Keep work and personal learning separate. HTML and PDFs embed their displayed records; do not publish private material. The hosted integration is paused. No extra service account, tunnel or connector is required.