Skip to content

Commit 767babc

Browse files
l-br1gitbook-bot
authored andcommitted
GITBOOK-1267: added archived banner to admin pages
1 parent 2735580 commit 767babc

51 files changed

Lines changed: 259 additions & 291 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
# Intersect Administration Policies
22

3+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
4+
35
* [**Administration Financial Audit Policy**](administration-financial-audit-policy.md)**:** To ensure a consistent understanding of Intersect’s policy regarding financial auditing, where Intersect is acting as an administrator for public proposals in accordance with the Cardano Constitution.
46
* [**Delivery Assurance Process and Best Practice Policy**](delivery-assurance-process-and-best-practice-policy.md)**:** To provide guidance to all beneficiaries working under contracts administered by Intersect, including smart contracts and legal contracts, to ensure delivery is executed transparently, with accountability, and in line with community expectations.
57
* [**Due Diligence Policy**](due-diligence-policy.md)**:** To establish a structured, comprehensive, and iterative framework for thoroughly investigating and verifying information before Intersect commits to new contractual relationships, transactions, or projects with new individuals or businesses.
68
* [**Technical Review Policy**](technical-review-policy.md)**:** To outline requirements, guidance where necessary, for review and technical audit of milestones (documents, designs, code, or other technical project artefacts) to ensure that the deliverables do not endanger the security, functionality, performance or long-term sustainability of the Cardano Blockchain.
79
* [**Wallet Address Change Policy**](/broken/pages/1hLHlKRTZjoM9rs8ZflB)**:** To ensure the secure and verified update of wallet addresses listed in vendor contracts after contract execution. This policy protects against unauthorized changes and potential fraud by enforcing a standardized identity verification process prior to approving any wallet address modification.
8-
* [**Committee Member Travel & Expense Policy**](committee-member-travel-and-expense-policy.md)**:** This policy provides clear guidance for Intersect Committee members and other approved external participants on travel and related expenses incurred on behalf of Intersect under contracts relating to Intersect Committees. It sets out rules for planning, booking, approvals, reimbursements, and per diem allowances to ensure fair, transparent, and cost-effective financial practices.
9-
10-
\\
10+
* [**Committee Member Travel & Expense Policy**](committee-member-travel-and-expense-policy.md)**:** This policy provides clear guidance for Intersect Committee members and other approved external participants on travel and related expenses incurred on behalf of Intersect under contracts relating to Intersect Committees. It sets out rules for planning, booking, approvals, reimbursements, and per diem allowances to ensure fair, transparent, and cost-effective financial practices.

archive/funding-administration-archive/intersect-administration-policies/administration-financial-audit-policy.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Administration Financial Audit Policy
22

3+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
4+
35
**1. Policy title:** Administration Financial Audit Policy
46

57
**2. Version:** 1.1

archive/funding-administration-archive/intersect-administration-policies/committee-member-travel-and-expense-policy.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Committee Member Travel & Expense Policy
22

3+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
4+
35
{% hint style="info" %}
46
Key Info
57

archive/funding-administration-archive/intersect-administration-policies/committee-treasury-management-policy-1.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Committee Treasury Management Policy
22

3+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
4+
35
**1. Policy Title:** Committee Treasury Management Policy
46

57
**2. Version:** 1.0

archive/funding-administration-archive/intersect-administration-policies/delegation-of-authority-form.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ description: >-
66

77
# Delegation of Authority Form
88

9+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
10+
911
1. **Authorized Signatory**\
1012
Each Party confirms that the individual signing this Agreement on its behalf (“Authorized Signatory”) has full authority to bind the Party to this Agreement.
1113
2. **Designation of Authorized Representatives**\

archive/funding-administration-archive/intersect-administration-policies/delivery-assurance-process-and-best-practice-policy.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Delivery Assurance Process and Best Practice Policy
22

3+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
4+
35
**1. Policy title:** Delivery Assurance Process and Best Practice Policy
46

57
**2. Version:** 1.1
@@ -26,7 +28,7 @@ This policy applies to the beneficiary, as defined below, who enters into contra
2628

2729
**9. Principles:**
2830

29-
This policy is founded on principles of openness, accountability, and the right to information, fostering trust among stakeholders/the community. It ensures a common understanding of Delivery Assurance requirements across all proposals. 
31+
This policy is founded on principles of openness, accountability, and the right to information, fostering trust among stakeholders/the community. It ensures a common understanding of Delivery Assurance requirements across all proposals.
3032

3133
**10. Definitions:**
3234

@@ -35,12 +37,12 @@ This policy is founded on principles of openness, accountability, and the right
3537
* **Milestone(s)** means the dates by which a part or all of the Services is to be completed, as set out in **a Statement of Work.**
3638
* [**Milestone Acceptance Form (MAF):** ](https://docs.google.com/document/d/1c1kC5q7LwHpQNGHdq9uXv5o5LNHXlDbxCJXtvMeenkA/edit?tab=t.0)This is a written attestation in the form of a standard template, submitted by a vendor, for each milestone.
3739
* **Intersect:** Intersect serves as an Administrator within Cardano’s funding ecosystem, helping to operationalize community-approved proposals by coordinating due diligence, contracting, and on-chain disbursements. This role is grounded in the principles of transparency, decentralization, and adherence to the Cardano Constitution.
38-
* **Statement of Work** means the document describing the Services and Deliverables to be provided by the Vendor, the Milestones, date of completion, expected quality standards, and associated fees. 
40+
* **Statement of Work** means the document describing the Services and Deliverables to be provided by the Vendor, the Milestones, date of completion, expected quality standards, and associated fees.
3941

4042
**11. Policy statements:**
4143

4244
* Beneficiaries remain fully responsible for delivering quality and value. Through transparency and sharing of milestone progress, reputation and open accountability keep the Cardano community is informed of development and treasury spend.
43-
* The MAF and invoice must be submitted within 5 business days of milestone completion. 
45+
* The MAF and invoice must be submitted within 5 business days of milestone completion.
4446
* If, in the opinion of Intersect (acting as the Administrator), the Milestone is incomplete or insufficiently completed, it is understood that payment may be delayed until the Milestone is complete. A consecutive failure to successfully complete a Milestone on two or more occasions may result in the termination of the Agreement or the corresponding Statement of Work.
4547

4648
**12. Roles and responsibilities:**
@@ -53,10 +55,10 @@ This policy is founded on principles of openness, accountability, and the right
5355

5456
* **Contract initiation:** When writing a SoW, consider how to clearly break up the work into tangible milestones. This will be checked and formally agreed with the Intersect Procurement team prior to contract signature.
5557
* **Milestone description:** When naming and describing a milestone, consider the following principles:
56-
* **Be concise and specific** - Avoid vague language or technical jargon. Aim for language that even a non-SME community member could understand.
57-
* **Be outcome-based** - Focus on what will be delivered, not what will be done. Think about what the end-user or Cardano community will receive as a result.
58-
* **Use consistent naming and numbering** - Number and name milestones clearly so they can be tracked and referenced easily throughout the project lifecycle.
59-
* **Set realistic, achievable milestones** - over-ambitious milestones can demotivate and cause delays. 
58+
* **Be concise and specific** - Avoid vague language or technical jargon. Aim for language that even a non-SME community member could understand.
59+
* **Be outcome-based** - Focus on what will be delivered, not what will be done. Think about what the end-user or Cardano community will receive as a result.
60+
* **Use consistent naming and numbering** - Number and name milestones clearly so they can be tracked and referenced easily throughout the project lifecycle.
61+
* **Set realistic, achievable milestones** - over-ambitious milestones can demotivate and cause delays.
6062
* **Timeline** - provide a realistic timeline that when the milestone will be completed by. Build in contingency to these dates where appropriate.
6163
* **Acceptance criteria:** Each milestone should have clear and testable acceptance criteria. These serve as the basis for milestone review and approval. Good acceptance criteria should be:
6264
* **Measurable and objective** – They can be independently verified by reviewers.
@@ -76,7 +78,7 @@ Intersect Delivery Assurance team will verify with the vendor that the third par
7678

7779
* **Contract management:** Once the milestone is complete, a completed [Milestone Acceptance Form (MAF)](https://docs.google.com/document/d/1c1kC5q7LwHpQNGHdq9uXv5o5LNHXlDbxCJXtvMeenkA/edit?tab=t.0) must be submitted to Delivery Assurance. Below is some guidance on what to include.
7880
* **Milestone Name(s) & Number(s):** To enable identification of the milestone, this should be written as per the contract.
79-
* **Milestone Description:** Include the milestone description as per the contract to help reviewers and the community to understand the milestone context. 
81+
* **Milestone Description:** Include the milestone description as per the contract to help reviewers and the community to understand the milestone context.
8082
* **Acceptance Criteria Met:** Explain how the work meets the contract’s acceptance criteria and describe what was delivered. To facilitate approval by the Delivery Assurance team, please include supporting links where possible. Ensure they are visible to stakeholders to support progress tracking and communication and also to support the Delivery Assurance process in verifying your work. These may include:
8183
* GitHub repositories or pull requests
8284
* Testnet/mainnet deployment addresses
@@ -95,7 +97,7 @@ Intersect Delivery Assurance team will verify with the vendor that the third par
9597
* Stakeholder Feedback Collection
9698
* Community Review / Public Sharing
9799
* Expert or Committee Review
98-
* **Public Communication Summary:** This section can be useful for the community to follow the progress of the project. Write a summary that can be shared publicly. Use the following pointers as guidance: Project Purpose, Context, Milestone Achievement, Benefits to the Community. Include a link to where the community can find project or progress updates. Below is some guidance on how to do this:
100+
* **Public Communication Summary:** This section can be useful for the community to follow the progress of the project. Write a summary that can be shared publicly. Use the following pointers as guidance: Project Purpose, Context, Milestone Achievement, Benefits to the Community. Include a link to where the community can find project or progress updates. Below is some guidance on how to do this:
99101
* Explain what the project is about
100102
* What was achieved in the milestone
101103
* Why it matters
@@ -106,14 +108,14 @@ Intersect Delivery Assurance team will verify with the vendor that the third par
106108
* Include a milestone roadmap / timeline and anticipated delivery dates.
107109
* Document progress, changes and blockers in GitLab or other publicly accessible platforms (eg a blog).
108110
* Community-friendly, plain English language.
109-
* Beneficiaries are also encouraged to host regular Ask Me Anything (AMA) sessions.
111+
* Beneficiaries are also encouraged to host regular Ask Me Anything (AMA) sessions.
110112
* **Signature Authorization:** The final section of the form requires signature from three parties: The person responsible for producing the work, Third-party Assurance and Intersect Delivery Assurance. Where applicable, make sure any other policy or constitutional requirement deemed necessary by the administrator has been fulfilled.
111113
* **Incomplete MAF:** If a MAF is deemed to be incomplete by the DA team, including missing the third-party assurance without any clear justification, the beneficiary will be informed and requested to provide supplementary information. If this causes substantial delays, then the payment for the milestone in question may be deferred to the next payment cycle. As per the policy statement (section 11), if there is a consecutive failure to successfully complete a Milestone on two or more occasions, this may result in the termination of the Agreement or corresponding Statement of Work.
112114

113115
**14. Monitoring and compliance:**
114116

115-
* **Monitoring:** Intersect, as the administrator, will monitor the completion of milestones, documentation, and payment throughout the contract lifecycle, overseeing that the appropriate delivery assurance is undertaken. 
116-
* **Compliance:** Significant compliance breaches may be disclosed to the community through public reports and escalated to DReps as appropriate, in alignment with transparency commitments. 
117+
* **Monitoring:** Intersect, as the administrator, will monitor the completion of milestones, documentation, and payment throughout the contract lifecycle, overseeing that the appropriate delivery assurance is undertaken.
118+
* **Compliance:** Significant compliance breaches may be disclosed to the community through public reports and escalated to DReps as appropriate, in alignment with transparency commitments.
117119

118120
**15. Review and amendment:**
119121

@@ -135,4 +137,3 @@ This policy should be read in conjunction with the following documents, guidelin
135137

136138
* [How to write Milestones](https://drive.google.com/file/d/18Yfv9rwKgayv1cVPzSj3QNOJP37UbIxZ/view?usp=drive_link)
137139
* [How to fill in the Milestone Acceptance Form](https://drive.google.com/file/d/16mflKXUKRVi1oJMh3_PomCqBJHdSH17L/view?usp=drive_link)
138-

archive/funding-administration-archive/intersect-administration-policies/due-diligence-policy.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Due Diligence Policy
22

3+
{% include "../../../.gitbook/includes/this-page-has-been-archived.md" %}
4+
35
**1. Policy title:** Due Diligence Policy
46

57
**2. Version:** 1.1
@@ -10,7 +12,7 @@
1012

1113
**5. Policy owner:** Head of Operations
1214

13-
**6. Policy sponsor:** Intersect Executive Director 
15+
**6. Policy sponsor:** Intersect Executive Director
1416

1517
_Updated on 27th June 2025_
1618

@@ -32,13 +34,12 @@ _Updated on 27th June 2025_
3234

3335
* **Beneficiary:** Individual and/or Company who will be receiving funds and/or entering into contractual relationships with Intersect or with CDH where Intersect is acting as its Administrator.
3436
* **Cardano Development Holdings (CDH):** CDH is a legal entity created to support the Cardano ecosystem by acting as the contracting counterparty for approved proposals.
35-
* **Intersect:** Intersect serves as an Administrator within Cardano’s funding ecosystem, helping to operationalize community-approved proposals by coordinating due diligence, contracting, and on-chain disbursements. This role is grounded in the principles of transparency, decentralization, and adherence to the Cardano Constitution. 
37+
* **Intersect:** Intersect serves as an Administrator within Cardano’s funding ecosystem, helping to operationalize community-approved proposals by coordinating due diligence, contracting, and on-chain disbursements. This role is grounded in the principles of transparency, decentralization, and adherence to the Cardano Constitution.
3638
* **Know Your Customer (KYC) -** This is a full check designed to identify and verify customers, ensuring compliance and preventing fraud.
3739
* **Identity Verification:** This is a core component, involving the collection and verification of personal information like name, date of birth, and address. Sumsub supports over 14,000 types of IDs from 220+ countries and can extract data in various languages. This can be done through document-based verification (uploading photos of government-issued IDs like passports, driver's licenses, or ID cards) or non-document methods that rely on government databases.
3840
* **Liveness and Deepfake Detection:** To ensure the person is real and present, Sumsub employs facial biometrics and liveness checks. This technology helps confirm that the provided ID document is truly in the possession of its owner and protects against sophisticated fraud like deepfakes.
3941
* **Proof of Address Verification:** Customers are required to provide proof of residence, often through documents like utility bills or bank statements (usually no older than 3 months), which are then verified for authenticity and consistency with the provided address and name.
40-
* **Anti-Money Laundering (AML) Screening:** Sumsub performs checks against sanctions lists, watchlists (including Politically Exposed Persons (PEPs)), and adverse media (negative news) to assess the customer's risk profile and ensure they are not involved in illicit activities.\
41-
42+
* **Anti-Money Laundering (AML) Screening:** Sumsub performs checks against sanctions lists, watchlists (including Politically Exposed Persons (PEPs)), and adverse media (negative news) to assess the customer's risk profile and ensure they are not involved in illicit activities.\\
4243
* **Know Your Business (KYB)** - this is a full check designed to verify the legitimacy of businesses and prevent fraud.
4344
* **Automated Corporate Registry Checks:** This process verifies and collects information about an organization and its beneficiaries from all registries. This verifies the organization's legal existence and ownership/management structure.
4445
* **Corporate AML Screening:** This is the process of assessing and verifying the legitimacy of corporate entities to ensure they are not involved in illicit activities like money laundering, fraud, or terrorist financing. It involves screening the company and its associated senior individuals against various databases for financial crime risks.
@@ -73,7 +74,7 @@ _Updated on 27th June 2025_
7374

7475
**13. Procedures:**
7576

76-
* Intersect Operational Services team will send the appropriate Sumsub KYC/KYB link to the individual for them to complete and submit the requested documents. 
77+
* Intersect Operational Services team will send the appropriate Sumsub KYC/KYB link to the individual for them to complete and submit the requested documents.
7778
* A KYC link is sent if the purpose of the agreement is with an individual.
7879
* A full KYB link is sent if the purpose of the agreement is with a company.
7980
* Sumsub will then take the responsibility of running the checks as described in section 10 of this document.
@@ -91,7 +92,7 @@ _Updated on 27th June 2025_
9192

9293
**15. Review and amendment:**
9394

94-
To ensure the policy remains current and effective, it will be reviewed at least annually. In response to significant organizational changes or regulatory updates, the policy will be updated as required by the Intersect Operational Services team and approved via the Intersect Executive team. 
95+
To ensure the policy remains current and effective, it will be reviewed at least annually. In response to significant organizational changes or regulatory updates, the policy will be updated as required by the Intersect Operational Services team and approved via the Intersect Executive team.
9596

9697
**16. Related documents/references:**
9798

@@ -102,9 +103,9 @@ This policy should be read in conjunction with the following documents, guidelin
102103
* Transparency Policy
103104
* External regulation and best practices
104105
* [SumSub](https://sumsub.com/)
105-
* [Sumsub Trust Centre](https://sumsub.com/sumsub-trust-center/) 
106-
* [CCN.com](https://www.ccn.com/education/crypto/10-countries-where-crypto-remains-banned/) - owned and operated by Find.co, is a media outlet dedicated to cryptocurrencies, business, finance and technology. \
107-
\
106+
* [Sumsub Trust Centre](https://sumsub.com/sumsub-trust-center/)
107+
* [CCN.com](https://www.ccn.com/education/crypto/10-countries-where-crypto-remains-banned/) - owned and operated by Find.co, is a media outlet dedicated to cryptocurrencies, business, finance and technology.\
108108
\
109109
\
110110
\
111+
\\

0 commit comments

Comments
 (0)