# Portal, connected records and the Commons index The entry page introduces Commons before the feed: its purpose, a small set of starting paths, and then the searchable collection. `portal/1_05-welcome.html` supplies this orientation. The three paths lead to the administrative-burden argument, record preparation, and the proposed audio workflow. The shared-records purpose article explains independent accountability, AI, and blockchain without making those concepts prerequisites for reading. The collection is a feed across subjects. Readers filter by subject or type, search, and open full articles in a reading window over the feed. Connected articles open in the same window; Escape or **Back to the feed** returns to the collection. The original frozen document remains available from each article. Goals, structure and the broader project argument live in the README and `about.html`. Verification, Pinata and Litecoin preparation live in `publish.html`. These are self-contained static editions; PHP builds them, but readers do not run PHP. ## This view and the public stream `portal.json` supplies this repository's initial collection. It names real frozen HTML editions, their section fragments, companion PDFs, authorship, review status and direct connections. It does not pretend the examples are already ledger publications. The initial assistance record is a blank template, not a signed attestation. The portal has an honest empty state for attestations. The portal currently reads the bundled collection and locally saved additions. The collection includes traffic enforcement, housing and credit reporting, technology, and Commons practice. Subject labels describe the current view; they are not requirements for publishing to Commons. The feed embeds the exact original HTML bytes for each edition, verifies their CIDs before reading, and copies only allowed article markup into the window. Sources stay with the article. Reading the bundled collection works offline without fetching a gateway or executing the original document's scripts. It makes no live chain request and claims no complete address history. Independent publishers do not need this catalog's approval to publish to the shared address. Later readers and scribes can retrieve those records and build their own views, as described in [the address and scribes](ADDRESS-AND-SCRIBES.md). ## Full entry URLs Every catalog entry has a stable static path, including entries omitted from the main feed. For example, `entry/debt-recollection.html` opens **Paying $1,000 to get past the process**, rather than the general court-process argument. Every reader shows its complete URL and a **Copy link** button. Article and company entries use the same path format. `sb.publish` creates `entry/.html` symlinks to `../index.html` when publishing the main portal. The path selects an entry inside that self-contained portal; links and original document references resolve from the site root. No server rewrite, framework, or CDN is required. These paths also work in an IPFS directory and a local checkout. Existing `#item=` links and `?item=` URLs remain supported. Closing a directly opened entry returns to the feed, and browser Back restores that entry. A stable entry URL selects the current edition. The separate CID and section fragment continue to identify exact historical bytes. A locally saved draft uses an absolute `index.html#item=` URL and still exists only in the browser where it was saved; copying its link does not publish its content. ## Company profiles and typed references The **Articles** and **Companies** collections are separate views. Open `index.html#view=companies` for the company directory, or `#item=company-experian` for a profile. Closing a profile returns to Companies; opening an argument selects Articles. Subject and search filters apply within the selected class. Catalog entries with `record_class: "company"` have `legal_name`, `role`, and `sources_checked` fields. Missing `record_class` means `article`, preserving existing editions and local contributions. Profiles use the existing `description` kind; the four contribution kinds and contribution wire format are unchanged. A reply to a company profile is a contribution, and does not inherit company-profile status. `related` connects articles; `companies` explicitly links company profile IDs. The PHP assembler rejects company links to missing or ordinary article entries. These links describe relevance, not an allegation that a company took part in any particular case. Company assertions name their sources and dates; a company description, complaint, procedural order, and settled finding retain their different meanings. Profiles can include a visible **John Rigler’s view** section for his opinions, observations, and criticism of the company's process. Those sections are part of the exact edition, with authorship and date, and are distinct from the cited official records. The catalog's `commentary` field records that attribution. General essays with `genre: "opinion"` display an Opinion label while retaining the existing `explanation` kind and contribution protocol. An opinion can make a strong argument without being presented as an adjudicated finding or a completed audit of every company's interface. **Download company reference** exports `commons/company-reference/1` JSON: ```json { "schema": "commons/company-reference/1", "company": {"id": "company-experian", "name": "Experian", "legal_name": "Experian Information Solutions, Inc."}, "profile": {"cid": "", "fragment": "company-experian"} } ``` This lets a later document distinguish a company reference from a reference to a general argument. The CID and fragment identify the profile edition; the label is not independent legal-identity verification. Case evidence must establish the company's involvement and its role in the specific event. ## B form: Commons as transport The intended meeting point is the Commons **transport tag**, the B / second semantic form. Chisel's cross-chain semantic parser calls `*Bx` transport. Its address generator also checks the actual network version byte. A literal `LBx` stem falls outside Litecoin mainnet P2PKH, so this repository already uses `LMx` as its explicit Litecoin transport-role encoding. Do not present this as a change to Chisel's literal B parser. The canonical mapping in this view is: | Property | Value | | --- | --- | | Chain | Litecoin mainnet | | Semantic form | B / transport | | Encoded prefix | `LMx` | | Readable body | `CoMMoNS` | | Full address | `LMxCoMMoNSzzzzzzzzzzzzzzzzzzZU8MFW` | The address is calculated with the existing 28-character stem plus checksum profile and tested independently for Litecoin version/checksum correctness. `thunderwords.js`, `portal-core.js` and `portal.json` must agree on it. The all-L address remains the broader Chisel index; it is not the Commons-only filter. The earlier LLx/LMx/LNx draft examples remain unchanged. ## Add below, preserve the parent, choose discoverability Open an entry, choose **Add below**, enter the contribution and choose its type. **Go** saves an unsigned record in this browser's localStorage. Every record has its own exact-byte raw CID and points to its parent's document CID plus section fragment. Replies to replies point to the previous contribution CID. Display aliases and titles are not the parent identity. The format is `commons/contribution/1`: ```text kind, title, text, author parent: { cid, fragment } indexed: true or false transport: Commons index address or null source: optional https:// or ipfs:// reference created: local ISO date/time ``` The author field is a supplied label. An attestation type is a statement of intent, not evidence of a cryptographic signature. A local timestamp is not a trusted timestamp. Byte checks, sources, signatures, chain receipts and editorial review are separate observations. The main view includes only indexed additions. An unindexed addition remains reachable through its parent and direct local link, but does not enter that main list. The portal opens one relationship at a time; it does not recursively fetch every reference or expand every possible branch. A different reader can choose broader traversal later. LocalStorage belongs to the browser origin. A GitHub Pages copy, an IPFS copy and a localhost copy have different stores. A local link does not publish the record to someone else's browser. Download the contribution to retain its exact bytes before changing browser/origin or clearing site data. No remote save, identity verification or transaction is implied by pressing Go. ## Dedicated Commons SHA-256 ledger view `reading/ledger/index.html` is a standalone browser view of BlockCypher-reported Litecoin mainnet transactions involving `LMxCoMMoNSzzzzzzzzzzzzzzzzzzZU8MFW`. It requires the transport output *and* a literal `sha256:` plus 64 lowercase hex digits in OP_RETURN before showing a transaction. It pages address history with the provider's `hasMore` cursor, filters locally by digest or txid, and links to Chisel's canonical transaction record. It does not expose the private source bytes or suggest the provider independently validates recording authenticity. A failed API call, missing page or provider rate limit is not an empty ledger. The [Chisel Commons hash handoff](https://github.com/johnrigler/chisel/tree/main/tools/commons) uses its existing Send payload importer with two unspendable recipients (the general Litecoin index and this Commons transport address). It is a new, distinct route from the legacy CertLedger hash tool; the earlier transport address and record formats are left intact. The digest remains exactly `sha256:` plus 64 hex characters, 71 ASCII bytes, not JSON. This page is a standalone view and is not yet embedded in the frozen Commons portal/CID edition. ## Publication path ### Reusable Experian form `entry/experian-correction-form.html` opens the reusable blank correction request. `reading/experian-form/index.html` provides local fill controls and a two-page print preview. The separately downloadable CID-named PDF remains blank. Form values stay in the tab's DOM; they are not saved as contributions or sent to the publishing workbench. A completed copy belongs to its consumer's case. The edition manifest records the exact PDF bytes, supplied template author, author-signature status and IPFS pin receipt separately. The current edition has a calculated raw CID but no signature or pin receipt. The intended final record is an author-signed PDF with the consumer fields still blank; signing changes its bytes and requires a new CID and edition. See [the form record](../reading/experian-form/README.md). From a saved contribution, **Download contribution** retains its exact JSON bytes. **Publish / announce** opens the publishing workbench in the same origin. It verifies and loads that local record, prepares `ipfs://` as the message, and carries over the Commons-index choice. An unindexed record uses the IPFS transport tag instead of accidentally selecting the Commons address. Connect an operator's Pinata account and explicitly pin the loaded file if a public IPFS copy is wanted. Preparing an announcement is another explicit step. The resulting draft includes the shared Commons output when selected, without duplicating an already-present transport address. Amounts remain unset and Chisel supplies transaction funding, fees, signing and broadcast. A ledger announcement can make a record discoverable through the shared tag. An untagged record can still exist at another CID or ledger reference; the default Commons view need not follow it. No live pin or broadcast was performed as part of this repository change. ## Build and checks The public website is served by GitHub Pages from `main` at the repository root. Changes, reader checks, and publication use the same branch; `portal-first` is an earlier development branch and is no longer a publication step. Verify the deployed page after a change before giving out its URL. Numbered HTML parts, ordinary source scripts and deliberate symlinks remain the publication mechanism. Historical CID-named HTML files are retained. ```bash source ~/commons/sb/publish.bash cd ~/commons sb.publish sb.publish ./sb/about.php about.html sb.publish ./sb/page.php publish.html node --test tests/core.mjs tests/portal.mjs tests/publication.mjs ``` Set `SB_PHP` to a PHP 8+ CLI binary when needed. `sb.publish` accepts the optional entry name `index.html`, `about.html` or `publish.html`, and changes only that entry symlink. Never redirect output through one of those links. The browser development check uses Playwright (`node tests/browser.cjs` with Playwright installed, or `COMMONS_PLAYWRIGHT` set to its module path). It tests connected reading, safe text rendering, saved replies, index filtering, reload, offline article windows, subject filters, publishing handoff, About navigation and a phone viewport. The static reader has no dependency on Playwright, Node, a framework or a CDN. ## Shared legal references `entry/legal-reference.html`, `entry/dispute-deadlines.html` and `entry/debt-remedies.html` are connected printable articles. `legal-references.json` provides the editable source, and `reading/law/edition.json` records the exact registry and rendered edition. New legal assertions should register their provisions with stable IDs and actor/trigger/deadline/limit fields. The imported inventory preserves earlier editions' legal sources without claiming a fresh review of each. See `RENT-ACCELERATION-CONTEXT.md` before applying these rules to an individual rental-dispute record. ## Generic authority-clarification correspondence `entry/authority-clarification.html` describes the reusable letter; `reading/correspondence/index.html` prints two Letter pages with blank fields or privately filled values. `reading/correspondence/source/fields.json` contains only field definitions. The runtime writes text nodes in the current tab and uses no storage, URL parameters or network submission. Print blank does not clear a filled private copy. The email-text control produces text for the user to review; it does not create a mail draft or send it. Real parties, source signatures, completed copies and delivery evidence belong in private Daisy.