OPL protocol corpus: Bitcom, B, AIP, MAP, Sigma, Addressing, 1Sat series, BAP, Bitcoin Schema (500-513)

README.md

@@ -220,6 +220,10 @@ BRC | Standard
 154  | [Pluggable Backup Services for BRC-140 Share Vaults](./wallet/0154.md)
 155  | [Pull-Based Receive Discovery](./wallet/0155.md)
 156  | [Latched 1Sat Provenance for Basket `1sat`](./tokens/0156.md)
+159  | [1Sat Ordinals — Single-Satoshi Tokens and Origin Tracking](./tokens/0159.md)
+160  | [1Sat Ordinals — Inscription Envelopes](./tokens/0160.md)
+161  | [BSV-21 Fungible Tokens (JSON / Legacy)](./tokens/0161.md)
+162  | [BSV-21 Fungible Tokens (Binary)](./tokens/0162.md)
 168  | [Verifiable Time Allocation](./apps/0168.md)
 169  | [Universal Handle Addressing and Resolution for the Metanet](./peer-to-peer/0169.md)
 218  | [Chat-Native Command Grammar for the Metanet](./apps/0218.md)
@@ -229,6 +233,16 @@ BRC | Standard
 225  | [Animated-QR Air-Gap Transport for Arbitrary Payloads (TKQR1)](./peer-to-peer/0225.md)
 226  | [Miner-Enforced Resale-Royalty Covenant Tokens (OP_PUSH_TX)](./tokens/0226.md)
 227  | [Frictionless On-Chain Onboarding via Pre-Funded Claimable Tokens](./apps/0227.md)
+500  | [Bitcom — Universal Bitcoin Computer: Decentralized Protocol Registry and Composition](./scripts/0500.md)
+501  | [B — Bitcoin Data Protocol](./scripts/0501.md)
+502  | [AIP — Author Identity Protocol](./scripts/0502.md)
+503  | [MAP — Magic Attribute Protocol](./scripts/0503.md)
+504  | [Sigma — Transaction-Bound Script Signatures](./scripts/0504.md)
+505  | [Outpoint Content Addressing](./outpoints/0505.md)
+508  | [1Sat Ordinal Collections](./tokens/0508.md)
+511  | [BAP — Bitcoin Attestation Protocol](./peer-to-peer/0511.md)
+512  | [Bitcoin Schema — Social Data Types](./apps/0512.md)
+513  | [Encrypted Group Messaging over Type-42 Key Derivation](./peer-to-peer/0513.md)
 
 ## License
 

SUMMARY.md

@@ -19,6 +19,7 @@
 * [NotaryHash — Privacy-Preserving Signed-Hash Notarization with SPV-Verifiable Certificates](./apps/0220.md)
 * [Block Media Format (BMF) — Composable On-Chain Audio/Video](./apps/0224.md)
 * [Frictionless On-Chain Onboarding via Pre-Funded Claimable Tokens](./apps/0227.md)
+* [Bitcoin Schema — Social Data Types](./apps/0512.md)
 
 ## Wallet
 
@@ -101,6 +102,11 @@
 * [Bare Multi-Signature](./scripts/0047.md)
 * [Pay to Push Drop](./scripts/0048.md)
 * [Bitcoin Script ASM Format](./scripts/0106.md)
+* [Bitcom — Universal Bitcoin Computer: Decentralized Protocol Registry and Composition](./scripts/0500.md)
+* [B — Bitcoin Data Protocol](./scripts/0501.md)
+* [AIP — Author Identity Protocol](./scripts/0502.md)
+* [MAP — Magic Attribute Protocol](./scripts/0503.md)
+* [Sigma — Transaction-Bound Script Signatures](./scripts/0504.md)
 
 ## Tokens
 
@@ -116,7 +122,12 @@
 * [1Sat Ordinals Basket Profile for BRC-46 / BRC-100](./tokens/0147.md)
 * [1Sat Provenance Remittance for Basket `1sat`](./tokens/0150.md)
 * [Latched 1Sat Provenance for Basket `1sat`](./tokens/0156.md)
+* [1Sat Ordinals — Single-Satoshi Tokens and Origin Tracking](./tokens/0159.md)
+* [1Sat Ordinals — Inscription Envelopes](./tokens/0160.md)
+* [BSV-21 Fungible Tokens (JSON / Legacy)](./tokens/0161.md)
+* [BSV-21 Fungible Tokens (Binary)](./tokens/0162.md)
 * [Miner-Enforced Resale-Royalty Covenant Tokens (OP_PUSH_TX)](./tokens/0226.md)
+* [1Sat Ordinal Collections](./tokens/0508.md)
 
 ## Overlays
 
@@ -166,6 +177,8 @@
 * [Fountain-Coded Air-Gap Transport for Arbitrary Payloads](./peer-to-peer/0141.md)
 * [Universal Handle Addressing and Resolution for the Metanet](./peer-to-peer/0169.md)
 * [Animated-QR Air-Gap Transport for Arbitrary Payloads (TKQR1)](./peer-to-peer/0225.md)
+* [BAP — Bitcoin Attestation Protocol](./peer-to-peer/0511.md)
+* [Encrypted Group Messaging over Type-42 Key Derivation](./peer-to-peer/0513.md)
 
 ## Key Derivation
 
@@ -189,6 +202,7 @@
 * [User Wallet Data Format](./outpoints/0038.md)
 * [User Wallet Data Format Encryption Extension](./outpoints/0039.md)
 * [User Wallet Data Synchronization](./outpoints/0040.md)
+* [Outpoint Content Addressing](./outpoints/0505.md)
 
 ## Opinions
 

apps/0146.md

@@ -102,7 +102,7 @@ Where a manifest states at least one condition, admission is self-service: a rea
 | `ungateBurn`                                      | decimal string | conditional | satoshis to burn to ungate; required while any condition is on |
 | `successor`                                       | handle         | no          | who may assume custody after dormancy, per 8.3                 |
 | `dormantAfter`                                    | blocks         | no          | holder silence after which `successor` may sign, per 8.3       |
-| `token` `vouch` `renounce` `quorum` `fee` `roles` | object         | no          | conditions, per 2.3                                            |
+| `token` `vouch` `renounce` `quorum` `timelock` `fee` `roles` | object         | no          | conditions, per 2.3                                            |
 
 An absent condition and one present with `"on": false` evaluate identically; the distinction exists for an editor holding a half-configured condition and nowhere else.
 
@@ -372,7 +372,7 @@ A **member** reads the room and posts in it. A **mod** also deletes messages and
 
 Banning is strictly downward and never sideways: no role bans its own rank. An admin banning an admin is the one action that can empty a room's admin set in a single click. **Custody is not a rank** — the holder sits underneath the ladder rather than on top of it, may act on any participant, and cannot be acted on; without that, an ungated room where everybody is an admin has nobody able to act on anybody. Deleting a message leaves a record that a message was removed rather than silently closing the gap, since a transcript that rewrites itself is one nobody can reason about afterwards.
 
-A **ban** is recorded as a statement against the handle under BRC-169 section 10.7, scoped to the room — so it has an author, a time and a claim, which a row in a ban array does not. It is **attributed**, reversing BRC-169 section 10.7.1's default: that default protects somebody speaking against a peer at their own risk, and a moderator acting inside a room they moderate is in the opposite position. A room-scoped statement does not contribute to the subject's standing anywhere else and does not satisfy a renounce gate in another room; being unwelcome in one room is not a reputation, and a mechanism letting one moderator's decision follow somebody across the network would be worse than the list it replaced. The subject is told, and by whom, and any role that could impose the ban can lift it. How a ban is then read back as a condition — where the record lives, what scoping means at evaluation time, and what lifting is — is section 4.5.
+A **ban** is recorded as a statement against the handle under BRC-169 section 10.7, scoped to the room — so it has an author, a time and a claim, which a row in a ban array does not. It is **attributed**, reversing BRC-169 section 10.7.1's default: that default protects somebody speaking against a peer at their own risk, and a moderator acting inside a room they moderate is in the opposite position. A room-scoped statement does not contribute to the subject's standing anywhere else and does not satisfy a renounce gate in another room; being unwelcome in one room is not a reputation, and a mechanism letting one moderator's decision follow somebody across the network would be worse than the list it replaced. The subject is told, and by whom, and any role that could impose the ban can lift it. How a ban is then read back as a condition — where the record lives, what scoping means at evaluation time, and what lifting is — is section 4.6.
 
 Closing a room is a signed statement carrying who closed it and when; conforming clients stop accepting posts and render the room as closed. History remains readable, because section 9 is why nothing here can un-deliver a message, and a client presenting closure as deletion has promised something no client can perform.
 

apps/0218.md

@@ -444,12 +444,12 @@ This document specifies what a command means, not how it looks, with three excep
 
 ### 11. Access Gates
 
-A room may condition **reading** it on facts about the reader — a token they hold, a vouch somebody signed, a statement written against them. That mechanism is specified in [BRC-190](./0190.md), which subsumes and replaces the sketch that previously stood in this section.
+A room may condition **reading** it on facts about the reader — a token they hold, a vouch somebody signed, a statement written against them. That mechanism is specified in [BRC-146](./0146.md), which subsumes and replaces the sketch that previously stood in this section.
 
 Two boundaries are worth restating here, because both are about this document.
 
-1. Access gates define no verbs and reserve none. Configuring a gate from a conversational interface is a matter for this document; what a gate *is* and how it evaluates is a matter for BRC-190.
-2. The `/gate` verb reserved in section 6 is a different thing and remains reserved. It is the **write** half — charging for entry, with custody, refunds, and a rule for what happens when the room ends. BRC-190 specifies the **read** half only.
+1. Access gates define no verbs and reserve none. Configuring a gate from a conversational interface is a matter for this document; what a gate *is* and how it evaluates is a matter for BRC-146.
+2. The `/gate` verb reserved in section 6 is a different thing and remains reserved. It is the **write** half — charging for entry, with custody, refunds, and a rule for what happens when the room ends. BRC-146 specifies the **read** half only.
 
 ## Security Considerations
 
@@ -478,6 +478,6 @@ Two boundaries are worth restating here, because both are about this document.
 ## References
 
 - [BRC-3: Digital Signature Creation and Verification](../wallet/0003.md)
-- [BRC-190: Access Gates for Metanet Rooms](./0190.md)
+- [BRC-146: Access Gates for Metanet Rooms](./0146.md)
 - [BRC-169: Universal Handle Addressing and Resolution for the Metanet](../peer-to-peer/0169.md)
 - [RFC 2119: Key words for use in RFCs to Indicate Requirement Levels](https://www.rfc-editor.org/rfc/rfc2119)