Terms of Service

1.1. Certive is a Document Trust Layer service developed and operated by Baliola, accessible via certive.io and app.certive.io.

1.2. Baliola is PT Baliola Adi Maha Duta, the legal entity operating Certive along with other products in its ecosystem, including the Mandala Application Chain blockchain infrastructure.

1.3. Mandala Chain is the blockchain network used by Certive to record digital document fingerprints permanently and in a tamper-proof manner.

1.4. User is any person who creates an account and uses Certive services, whether as a Document Holder, Issuer, or Organization member.

1.5. Verifier is anyone who inspects the authenticity of a document via a Certive verification link, with or without an active account.

1.6. Issuer is a User who issues Documents through Certive, either as an individual or on behalf of an Organization.

1.7. Document Holder (Holder) is a User who receives and stores Documents issued to them.

1.8. Organization is an entity established within Certive by a User, consisting of one or more Users with their respective roles, to collectively issue Documents on behalf of an institution.

1.9. Document is any digital file issued by an Issuer through Certive to record its integrity and origin.

1.10. Digital Fingerprint (Hash) is a unique representation of the content of a Document, generated through a computational process on the Issuer’s own device, used by Certive to prove Document integrity without ever storing the Document itself.

1.11. Verification Link is a unique link accompanying each issued Document, which can be used by anyone to check the integrity and origin of that Document.

1.12. Issuer Trust Level is the classification displayed by Certive representing the extent to which an Issuer’s identity has been reviewed, as governed in Article 9.

1.13. Crypto Wallet is a blockchain-based digital wallet that can optionally be linked to a Certive account, as governed in Article 12.

1.14. KPG Token is the native token of the Mandala Chain network that Users can use to participate in the Web3 Staking program as governed in Article 15.

1.15. Service Plan is the paid or free tier selected by a User or Organization to use Certive, as governed in Article 14.

1.16. Certificate of Document Integrity is an official PDF proof document issued by the Certive system, containing document metadata summary, validity status (STAMPED), Issuer and Organization identity details, public verification QR code, and blockchain transaction recording proof (Transaction Hash) proving document integrity and origin.

1.17. Organization Cloud Storage is a third-party cloud storage media service (such as Google Drive) connected to an Organization account in Certive, which serves to automatically store stamped original document files under the full control and ownership rights of that Organization.

1.18. OpenCerts: An internationally recognized blockchain-based open-source framework standard for issuing and verifying digital certificates (initiated by GovTech Singapore).

1.19. Blockchain Identity (BID): Certive’s blockchain-based decentralized identity system (Decentralized Identity) providing unique cryptographic identity to issuing institutions and users.

1.20. Decentralized Identifier (DID): A W3C-standard unique decentralized identifier address used to verify the cryptographic identity of an Issuer or Holder without depending on a centralized authority.

1.21. Verifiable Credentials (VC): A structured credential data file in .json format issued based on the W3C Verifiable Credentials Data Model v2.0 specification, containing verified claims regarding one or more subjects (identity, document, membership, or qualification) through a standardized data structure attaching cryptographic proof.

1.22. Credential Payload: Data or metadata contained within a Verifiable Credentials (.json) file, stored and held independently by the Document Holder (Self-Sovereign Identity).

1.23. On-Chain Revocation: An issuer’s action to change the validity status of a credential or document in a blockchain smart contract from active (valid) to revoked.

2.1. These Terms and Conditions apply from the moment you complete the Certive account registration process and remain effective as long as you maintain an active account or use Certive services, including as a Verifier without an account.

2.2. Baliola may update these Terms and Conditions from time to time as governed in Article 19. Continued use of the service after updates take effect constitutes your consent to such changes.

2.3. If you use Certive as a member of an Organization, these Terms and Conditions apply to you personally as well as to the Organization you belong to, to the extent relevant to your role within it.

3.1. Certive is a service that helps institutions digitally issue official documents so that anyone can verify that a file has not been altered since it was first issued, and trace who issued it.

3.2. Certive is primarily intended for notaries and law firms, universities, government ministries/agencies, state-owned enterprises (SOEs), and private enterprises that issue, distribute, or verify official documents between institutions.

3.3. Original Document files are never stored on Certive servers. Each Document is processed directly on the Issuer’s device to generate a Digital Fingerprint, and only that Digital Fingerprint is permanently recorded onto the Mandala Application Chain network. Document owners always retain their original files.

3.4. Users log in to Certive using an email address and password. There is no requirement to understand blockchain technology or possess a Crypto Wallet to use Certive’s core services, including issuing Documents.

3.5. Certive proves that a file has not changed since issuance and who issued it. Certive does not prove that the content of the Document is truthful, and does not prove that the Issuer is legally legitimate, unless the Issuer has reached the highest trust level as governed in Article 9. See Article 15 for full limitations.

3.6. Certive integrates W3C Verifiable Credentials and OpenCerts standards. Digital credential files in .json format issued through Certive are interoperable and can be independently verified via Certive’s public verification portal as well as global OpenCerts portals.

4.1. Each User is identified by a personal or corporate email address. Before being able to issue or hold Documents, a User’s email address must be verified via a link sent to their inbox.

4.2. Account registration is currently not open to the general public. During this launch phase, new accounts can only be created through one of the following three pathways.

4.3. Baliola may perform manual eligibility reviews of prospective Issuers, including checking professional registration numbers or business entity documents, especially for notaries and law firms, as a basis for increasing the Issuer Trust Level as governed in Article 9.

4.4. For account security, Certive temporarily limits repeated failed login attempts within a short timeframe, and login sessions will automatically expire after a certain period requiring Users to log back in periodically.

4.5. You are fully responsible for maintaining the confidentiality of your account password and for any activity occurring through your account. Immediately report to Baliola via the channel in Article 22 if you suspect unauthorized access to your account.

4.6. Possessing a Crypto Wallet is entirely optional and is never a prerequisite to create an account, hold any role, or use any feature in Certive, including issuing Documents.

5.1. Every active account automatically acts as a Document Holder, entitled to receive Documents issued to them, view their full Document history, and share Verification Links with third parties.

5.2. Other roles are contextual as follows.

5.3. A person can issue Documents without having a Crypto Wallet, provided their email address is verified, their account is not suspended, and they issue as an individual or as an Organization member granted issuance permissions.

5.4. The ability to issue Documents is separate from the Trust Level displayed to Verifiers. Someone who has just verified their email can issue Documents, but those Documents will display an “Unverified Issuer” label until their trust status is elevated as governed in Article 9.

5.5. There are two access levels for Verifiers. Verifiers who are logged in (authenticated) obtain complete verification results along with a limited history of the Document, including when the Document was issued, any updates or revocations that occurred, and their own verification history. Verifiers who are not logged in (public) only obtain core verification results without Document history.

6.1. Any User with an active account can establish an Organization in Certive. The Organization founder automatically becomes the Owner. Other members are invited via email, and one person can belong to multiple Organizations with different roles in each Organization.

6.2. Roles within an Organization are defined as follows.

6.3. Organizations on the Enterprise Service Plan must maintain at least two active Admins at all times. Certive will reject Admin removal requests that would cause the active Admin count to fall below two, to prevent Organizations from becoming locked without an administrator.

6.4. If a member is removed from an Organization, all Documents previously issued by that member on behalf of the Organization remain valid and permanently recorded. Membership changes do not invalidate prior issuance records.

6.5. Organizations may optionally require members to use email addresses under their verified domain when issuing Documents on behalf of the Organization.

6.6. The Organization Owner possesses exclusive authorities not accessible to other roles, including:

• Connecting, configuring, or disconnecting Organization Cloud Storage (Google Drive) integrations.
• Transferring primary ownership of the Organization to another user.
• Requesting permanent deletion of the Organization account from the Certive platform by contacting Baliola via official channels in Article 22.

6.7. Organization Owners and Admins are responsible for ensuring every member granted issuance permission understands and complies with these Terms and Conditions, including the issuance liability statement in Article 7.5.

7.1. When an Issuer issues a Document, the following process applies sequentially.

1. The Document file is processed directly on the Issuer’s own device to generate its unique Digital Fingerprint. The original file is never sent or stored on Certive servers.
2. The Issuer fills in recipient information including email address, Document type, brief description, and other fields according to user needs.
3. Certive verifies the Issuer’s eligibility as governed in Article 5.3. Ineligible issuances are rejected with clear reasons.
4. The Digital Fingerprint is checked against Certive’s internal registry to ensure it has not been previously recorded. Documents whose Digital Fingerprint is identical to a previously issued Document are rejected as duplicates.
5. After passing duplicate checks, the Digital Fingerprint is permanently and tamper-proof recorded onto the Mandala Application Chain network through Certive’s additional security mechanisms. This record cannot be altered or deleted by anyone once successful, including Baliola itself.
6. Once recording is successfully confirmed, the Document achieves active status, and the recipient receives an email notification containing a Verification Link that can be used anytime in the future.

7.2. If recording fails due to temporary technical disruption, the system automatically retries. The Document is not displayed as “active” until its recording is successfully confirmed.

7.3. Bulk Issuance. Certive enables Issuers to upload and issue multiple Documents simultaneously in a single issuance batch, ranging from a minimum of two to a maximum of five hundred Documents per batch, unless specified otherwise under the Enterprise Service Plan. Each Document in a batch remains individually verifiable by its respective recipient, and each recipient receives their own Verification Link.

7.4. Duplication Prevention. Each file can only be recorded once in Certive. Attempts to issue a file with identical content to an already recorded Document will be rejected. Duplication rejection messages do not disclose the identity of other Issuers or metadata of previously recorded Documents.

7.5. Issuer Liability Statement. Before issuing a Document for the first time, each Issuer must agree to a liability statement confirming that the Issuer assumes full responsibility for the legitimacy, truthfulness of content, and propriety of issuing Documents through Certive. Certive operates as an integrity recording service, not as a party guaranteeing or authenticating Document contents.

7.6. Every issued Document is clearly recorded with the identity of its Issuer. There is no anonymous issuance in the Certive system.

7.7. Certificate of Document Integrity Feature. Users or Organizations that have successfully issued a Document can generate and download a PDF Certificate of Document Integrity. This certificate serves as an official proof of validity sheet equipped with a QR Code for fast public verification, metadata summary, full issuer identity, and blockchain recording details.

7.8. Issuers or Organizations can issue 3 (three) types of Verifiable Credentials through Certive:

1. Certificate of Document Integrity: Credential proving the authenticity and integrity of document files.
2. Certificate of Organization Verification: Credential proving the validity of identity and official organization qualifications (BID).
3. Certificate of Membership: Credential proving membership status and individual role within an organization.

7.9. The Issuer is fully responsible for the accuracy, truthfulness, and validity of personal data or subject information entered into the Credential Payload (.json). Baliola does not perform substance verification on personal data entered by the Issuer into the payload.

8.1. Anyone, with or without an account, can verify a Document using its accompanying Verification Link by uploading a copy of the file to be checked.

8.2. Certive checks whether the Digital Fingerprint of the uploaded file matches the one recorded when the Document was first issued. Verification results are available in under sixty seconds under normal operating conditions.

8.3. Verification results are never presented as a single “Authentic” label. Results are always broken down into three independent signals as follows.

8.4. Proven unchanged file integrity is never by itself sufficient to display an “Authentic” or “Safe” label. The Issuer Trust Level is always displayed alongside and with equal weight: fraudulent Documents issued by irresponsible parties still appear “intact” if unaltered since initial issuance.

8.5. Possible results displayed to Verifiers include intact file with Unverified Issuer, intact file with Registered Issuer status, Document revoked, file mismatch or altered, Issuer currently suspended, Document not found, and Document still processing recording.

8.6. Each verification result page includes an explicit explanation of what is proven and what is not proven by the result, as further detailed in Article 15.

9.1. Because full legal identity verification for every Issuer is not available in the current service phase, Certive displays Issuer Trust Levels as the following progressive tiers.

9.2. The “Registered Issuer” level is not legal identity verification and is not equivalent to the “Verified Identity” level. This status merely states that the Certive Team has performed a manual review of the relevant Issuer’s eligibility.

9.3. Accountability as a protective layer. While full legal identity verification is unavailable, Certive relies on three accountability mechanisms: mandatory liability statements for every Issuer prior to initial issuance, full Issuer identity traceability on every issued Document, and abuse reporting and suspension mechanisms as governed in Article 11.

9.4. Baliola reserves the right to unilaterally review and elevate an Issuer’s Trust Level based on supporting documents submitted by the Issuer, and reserves the right to refuse such elevation without obligation to explain detailed reasons to the relevant Issuer, provided such decision is made in good faith.

10.1. An Issuer may revoke a Document they have issued along with the reason for revocation. Revocation is permanently recorded onto the Mandala Application Chain network and cannot be undone.

10.2. Once a Document is revoked, any subsequent verification of that Document will display a “Revoked” status along with the reason provided by the Issuer at the time of revocation.

10.3. Revocation is performed individually for each Document. Bulk revocation of all Documents in an issuance batch simultaneously is not supported in the current service phase.

10.4. Revocation does not erase the record that the Document was once issued. The original issuance record remains permanently stored on the blockchain as part of the audit trail. Only its validity status changes.

10.5. In addition to issuance and revocation, Issuers or Organization Admins can manage the Document validity lifecycle through the following mechanisms:

• Document Hiding (Unpublish): Issuers or Organization Admins have the right to change Document access status to Unpublish to hide Document details from public verification browsers. This action does not delete or alter transaction records stored on the blockchain network.
• Document Version Updates (Update): Issuers or Organization Admins can upload newer versions of previously issued Documents (v1, v2, etc.). Each version update is recorded as a new history entry on the blockchain without erasing the audit trail (Document Timeline) of prior document versions.
• Stamping Retry Processing (Retry Stamp): If Digital Fingerprint recording to the blockchain network experiences delays (pending) or technical systemic failures, Issuers or Organization Admins can trigger the Retry Stamp function to reprocess recording until active status (STAMPED) is achieved.

11.1. Any Verifier or Document Holder who suspects abuse, including fraudulent Document issuance or Issuer identity fraud, may report the matter to Baliola via the channel in Article 22.

11.2. Each report is reviewed by the Certive Team. If a report is proven valid, Baliola reserves the right to suspend the relevant Issuer’s ability to issue new Documents, without prior notice in urgent circumstances.

11.3. Documents issued prior to suspension remain permanently recorded and are not deleted, but are displayed to Verifiers with a warning that the Issuer is currently in suspended status.

11.4. Baliola reserves the right, in its sole discretion, to suspend or terminate access for any User proven to have violated these Terms and Conditions, as further governed in Article 18.

12.1. Users familiar with blockchain technology may optionally link their Crypto Wallet to their Certive account via account settings.

12.2. Linking a Crypto Wallet is never required to use any feature in Certive, including issuing Documents. Its benefits are supplementary: reinforcing proof that issuance was performed by the owner of the relevant cryptographic key.

12.3. Users are solely responsible for the security of their Crypto Wallet private keys. Baliola does not store, possess access to, or assume liability for loss of access to a User’s personal Crypto Wallet.

12A.1. Separation of Personal Google Account and Organization Storage Functions. Certive services strictly distinguish between using Google accounts for personal authentication versus organization storage integrations:

• Personal Google Account (Single Sign-On / SSO): Used at the individual account level (in the Personal Account menu) specifically for registration, login identity verification, and User account security.
• Organization Cloud Storage: Used at the organization level (in the Organization Management Settings -> Storage menu) to automatically store stamped original document files to Google Drive.

12A.2. Independence of Organization Storage Email Address. The email address of the Google Drive account connected as Organization Cloud Storage is not required to match the Google account email address used by Users (both Owners and Admins) to register or log into the Certive platform. Organizations are free to designate and use dedicated institutional Google Workspace/Drive accounts belonging to the company or team.

13.1. Document files are never stored on Certive servers in any form. This is a core and permanent privacy commitment of the Certive service.

13.2. If an Organization enables third-party cloud storage integration features (such as Google Drive), uploaded original files are sent directly to the connected Organization-owned storage account. Under these conditions, Certive only stores issuance metadata and delivery reference links, while storage, governance, and security of original files remain subject to the terms, conditions, and controls of that third-party storage provider.

13.3. Certive only stores the Digital Fingerprint of each successfully issued Document inside an internal registry used for duplication checking as governed in Article 7.4. This registry never stores original files, only digital fingerprints.

13.4. What is recorded on the blockchain is not raw Digital Fingerprints, but derived values processed beforehand by Baliola using Certive’s secret key. External parties possessing only a copy of a file cannot compute and match that value independently without Certive’s involvement. This mechanism provides additional privacy benefits. Blockchain verification still requires active involvement of Certive as key holder, and Baliola is developing key governance and continuity procedures, with material developments communicated to Users.

13.5. User passwords and sensitive data are stored using industry-standard encryption, and all data communication between User devices and Certive systems is encrypted.

13.6. Certive processes User personal data in accordance with applicable Indonesian Personal Data Protection laws, applying data minimization principles: collecting and storing only data necessary to operate the service.

13.7. Access to the Digital Fingerprint registry is internally restricted, and all access is logged as part of Baliola’s security audit trail.

13.8. Certive privacy policies and data handling are detailed in the Certive Privacy Policy, an integral part of these Terms and Conditions.

13.9. On-Chain Cryptographic Data and Non-PII. Users understand and agree that data recorded onto the Mandala Chain blockchain network consists solely of anonymous cryptographic values (Cryptographic Hash / Merkle Root) and Decentralized Identities (BID/DID). These on-chain records do not contain Personally Identifiable Information (PII) in raw text. Therefore, permanent (immutable) hash recording on the blockchain does not violate Personal Data Protection provisions under Indonesian PDP Law or Singapore PDPA.

13.10. Exercise of Data Subject Rights: In accordance with Indonesian PDP Law and Singapore PDPA:

1. Right to Access & Rectify Data: Users may request account profile data corrections through the Certive application.
2. Right to Off-Chain Account Erasure (Right to Erasure): Users have the right to request deletion of their account and personal data stored in Certive’s off-chain operational database by contacting support@baliola.io.
3. Blockchain Record Exception: Users understand that due to the tamper-proof technical nature of blockchain, cryptographic transaction proofs (Transaction Hash) and revocation status records (Revocation Status) previously recorded on the blockchain cannot be deleted or altered, but such data contains no raw personal User data.

14.1. Service Plans and Billing. Payment for Certive Service Plans can be processed through several billing model options depending on the plan selected by the Organization, including recurring subscriptions (Subscription), prepaid Doc Credits, Pay As You Go usage, hosted invoices, special discounts, or custom commercial arrangements for institutional clients.

14.2. Service Plan Upgrades and Downgrades. Service plan upgrades or quota additions take effect immediately upon successful payment confirmation. Service Plan downgrades take effect at the start of the next billing cycle and do not reduce fees already paid for the current billing cycle.

14.3. Payment Methods. Payment transactions can be completed through official channels available in the checkout flow, such as Bank Transfers, Credit/Debit Cards, E-Wallets, QR Code Payments (QR Payment), and Retail Outlets. Currency details, invoices, and spending limits are clearly displayed before transactions are confirmed.

14.4. Refund Policy. All fees paid are non-refundable, unless determined otherwise in writing by Baliola or required by applicable legal provisions.

14.5. Payment Failures. Repeated payment processing failures may result in the account or Organization being downgraded to the Free Plan or temporarily suspended until payment is resolved, with prior notification to the affected User.

15.1. Certive provides Document integrity and origin recording services. Certive proves who issued a Document, when it was issued, and that the file has not changed since then, ensuring the Issuer can be traced and held accountable. Certive does not state that the content of the Document is truthful.

15.2. Specifically, Certive does not resolve and cannot be claimed to resolve the following:

• The truthfulness of substance or content of a Document.
• The legal validity of an Issuer, unless that Issuer has reached the “Verified Identity” level as governed in Article 9, which at the time of drafting these Terms and Conditions is not yet activated.
• Misuse by an Issuer whose identity is legitimate but acts with bad intent, including issuing Documents with untruthful content.

15.3. Each verification result displayed by Certive is accompanied by an explicit explanation of what is proven and what is not proven by the result. Verifiers in doubt regarding the substantive validity of a Document are advised to confirm directly with the Issuer through official Issuer channels outside the Certive system.

15.4. Certive services are provided on an “as is” and “as available” basis. Baliola strives to maintain high availability during operating hours, but does not guarantee the service will always be error-free, uninterrupted, or delay-free.

15.5. To the extent permitted by applicable law, Baliola’s liability for damages arising from the use of Certive services is limited to the amount of fees paid by the User to Baliola for the relevant Service Plan in the preceding twelve months. Baliola is not liable for indirect damages, consequential damages, or lost profits arising from the use or inability to use Certive services.

15.6. The provisions in Article 15.5 do not apply to damages arising from gross negligence or intentional misconduct by Baliola, or in other cases that cannot be limited under applicable law.

15.7. Where verification is conducted via third-party OpenCerts portal opencerts.io, Baliola is not responsible for the availability, technical issues, or policy changes of such third-party portal, provided cryptographic proof recording on the Mandala Chain network remains valid.

16.1. Users must provide truthful and accurate information during account registration and throughout their use of Certive services.

16.2. Users are prohibited from issuing Documents that they know or should reasonably suspect contain false, misleading information, or infringe upon the rights of others, including intellectual property and privacy rights.

16.3. Users are prohibited from using Certive services for any purpose violating applicable laws in Indonesia or in the jurisdiction where the User resides.

16.4. Users are prohibited from attempting to access, disrupt, or damage Certive systems, networks, or infrastructure, including unauthorized attempts to access the Digital Fingerprint registry or Certive secret keys.

16.5. Users are prohibited from using another party’s account without permission, or misusing invitation mechanisms to register accounts for parties unauthorized to receive such invitations.

16.6. Violations of this Article 16 may result in access suspension or termination as governed in Article 11 and Article 18, without prejudice to Baliola’s right to pursue other available legal remedies.

17.1. All intellectual property rights over the Certive platform, including software code, interfaces, logos, and Certive trademarks, are owned by Baliola or its licensors, and protected by applicable intellectual property laws.

17.2. These Terms and Conditions do not grant Users any ownership rights over the Certive platform, except for limited, non-exclusive, non-transferable rights to access and use Certive services in accordance with these Terms and Conditions.

17.3. Copyrights and intellectual property over the content of each Document issued through Certive remain owned by the legitimate Document owner. Certive only records the Digital Fingerprint of the Document and claims no rights over its content.

18.1. Users may terminate their use of Certive services at any time by closing their account via account settings or by contacting Baliola via the channel in Article 22.

18.2. Baliola reserves the right to suspend or terminate User access to Certive services, at any time with or without prior notice, in the event of violations of these Terms and Conditions, suspected abuse as governed in Article 11, or mandatory legal obligations.

18.3. Account termination does not erase Document issuance, revocation, or verification records permanently logged onto the blockchain prior to termination, owing to the permanent and tamper-proof nature of such records as governed in Article 3.3.

18.4. Article 13, Article 15, Article 17, and Article 20 remain effective after service termination, to the extent relevant to obligations or rights arising prior to termination.

19.1. Baliola reserves the right to modify, add, or discontinue Certive service features from time to time to enhance service quality and security.

19.2. Baliola reserves the right to update these Terms and Conditions at any time. Material changes will be notified to Users via registered email or in-platform notifications at least seven calendar days prior to taking effect.

19.3. If a User does not agree to amendments, the User may terminate service use as governed in Article 18 before amendments take effect. Continued use of services after the effective date of amendments constitutes agreement to such changes.

20.1. These Terms and Conditions are executed and interpreted under the laws of the Republic of Indonesia.

20.2. Any dispute arising from or related to these Terms and Conditions shall first be attempted to be resolved amicably through consensus between the parties.

20.3. If an amicable settlement is not reached within a reasonable period, the dispute shall be resolved through the competent District Court in accordance with Baliola’s legal domicile, without prejudice to the parties’ rights to pursue other dispute resolution mechanisms agreed upon in writing.

21.1. If any provision of these Terms and Conditions is declared invalid or unenforceable by a competent court, remaining provisions in this document shall remain in full force and effect.

21.2. Baliola’s failure to enforce any right or provision in these Terms and Conditions shall not be construed as a waiver of such right in the future.

21.3. These Terms and Conditions, together with the Certive Privacy Policy and separate commercial agreements applicable to Enterprise Plans, constitute the entire agreement between the User and Baliola regarding the use of Certive services, superseding any prior oral or written agreements regarding the same.

21.4. Users may not assign or transfer their rights and obligations under these Terms and Conditions to another party without prior written consent from Baliola. Baliola may assign its rights and obligations under these Terms and Conditions in connection with a reorganization, merger, or business transfer, with notice to Users.

22.1. Any questions, complaints, or reports of suspected abuse regarding Certive services, including those governed in Article 11, may be submitted via email: support@baliola.io.

22.2. Baliola responds to every submitted complaint within a reasonable timeframe, and follows up on abuse reports in accordance with review procedures governed in Article 11.