adding new file/structure

Author: kmurphypolygon

docs/cdk/edge-suggestion.md

@@ -1,8 +1,10 @@
-Suggestion: migrate the whole of the current WIKI docs into the repo.
+So, we could put the whole thing https://wiki.polygon.technology/docs/edge/ here. However, there may be a better option.
 
-[https://github.com/0xPolygon/polygon-edge](https://github.com/0xPolygon/polygon-edge)
+Suggestion: migrate the whole of the current WIKI docs into the repo:
 
-In a `docs` directory which spins up how it looks currently in the wiki as a docusaurus site, or we can create a simpler static site if required. We can also review and edit like we're doing here but it might not be priority.
+https://github.com/0xPolygon/polygon-edge
+
+Into a `docs` directory which spins up how it looks currently in the wiki as a docusaurus site, or we can create a simpler static site if required. We can also review and edit like we're doing here but it might not be priority.
 
 To discuss with Gabriel.
 

docs/cdk/how-to/manage-policies.md

@@ -1,29 +1,31 @@
+## Policy overview
+
+A **policy** is a set of rules that govern what actions are allowed or denied in the transaction pool. 
+
+- **Fine-grained control**: Developers can specify policies at a granular level, allowing or denying specific actions for specific addresses.
+- **Dynamic updates**: Policies and ACLs can be updated on-the-fly without requiring a node restart.
+- **Database-backed**: All policy data is stored in a PostgreSQL database.
+- **Extensible**: New policies can be easily added to the system.
+
 ## Validium node
 
-A **policy** is a set of rules that govern what actions are allowed or denied in the transaction pool. Currently, there are two defined policies:
+### Policies
+
+Currently, there are two defined policies:
 
 - **SendTx**: governs whether an address may send transactions to the pool.
 - **Deploy**: governs whether an address may deploy a contract.
 
 The CDK validium node offers policy management features that include allowlisting[^1], denylisting[^2], and access control lists (ACLs)[^3]. These features are beneficial for validium-based app-chains that require fine-grained control over transaction pools. 
 
-## Architecture
+### Code definitions
 
-The architecture is divided into the following main components:
-
-- **Policy management layer**: Defined in `policy.go`, this layer is responsible for the core logic of policy management.
-- **Data layer**: Defined in `pgpoolstorage/policy.go`, this layer interacts with the data layer (PostgreSQL database) to store and retrieve policy and ACL data.
-- **Policy definitions**: Defined in `pool/policy.go`, this layer contains the data structures and utility functions for policies and ACLs.
-- **Policy interface**: Defined in `pool/interfaces.go`, this interface outlines the methods that any concrete type must implement to be considered a policy in the system.
-
-## Policy features
-
-- **Fine-grained control**: Developers can specify policies at a granular level, allowing or denying specific actions for specific addresses.
-- **Dynamic updates**: Policies and ACLs can be updated on-the-fly without requiring a node restart.
-- **Database-backed**: All policy data is stored in a PostgreSQL database.
-- **Extensible**: New policies can be easily added to the system.
+- **Policy management**: [`cmd/policy.go`](https://github.com/0xPolygon/cdk-validium-node/blob/5399f8859af9ffb0eb693bf395e1f09b53b154de/cmd/policy.go) contains the core logic of policy management.
+- **Policy definitions**: [`pool/policy.go`](https://github.com/0xPolygon/cdk-validium-node/blob/5399f8859af9ffb0eb693bf395e1f09b53b154de/pool/policy.go) contains structs and utility functions for policies and ACLs.
+- **Data**: [`pgpoolstorage/policy.go`](https://github.com/0xPolygon/cdk-validium-node/blob/5399f8859af9ffb0eb693bf395e1f09b53b154de/pool/policy.go) interacts with the data layer (PostgreSQL database) to store and retrieve policy and ACL data.
+- **Policy interface**: [`pool/interfaces.go`](https://github.com/0xPolygon/cdk-validium-node/blob/5399f8859af9ffb0eb693bf395e1f09b53b154de/pool/interfaces.go#L42) contains a `policy` interface which defines the methods that policies must implement.
 
-## Instructions for using policies
+### How to use a policy
 
 | Command name | Description                                           | Flags & parameters                                                                                      |
 |--------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
@@ -36,15 +38,15 @@ The architecture is divided into the following main components:
 !!! note
     For the examples, we are using a `deploy` policy.
 
-### Add addresses to a policy
+#### Add addresses
 
 To add one or more addresses to a specific policy, you can use the `policy add` command. If you have a CSV file containing the addresses, you can use the --csv` flag.
 
 ```bash
 docker exec -it cdk-validium-aggregator /app/cdk-validium-node policy add --policy deploy 0xAddress1
 ```
 
-### Remove addresses from a policy
+#### Remove addresses
 
 To remove addresses from a policy, you can use the `policy remove` command.
 
@@ -56,15 +58,15 @@ docker exec -it cdk-validium-aggregator /app/cdk-validium-node policy remove --p
 docker exec -it cdk-validium-aggregator /app/cdk-validium-node policy remove --policy deploy --csv addresses.csv
 ```
 
-### Clear all addresses from a policy
+#### Clear all addresses
 
 To remove all addresses from a policy's ACL, you can use the `policy clear` command.
 
 ```bash
 docker exec -it cdk-validium-aggregator /app/cdk-validium-node policy clear --policy deploy
 ```
 
-### Describing policies
+#### Get information about a policy
 
 To get information about a specific policy or all policies, you can use the `policy describe` command.
 

docs/cdk/performance-benchmarks.md …/specification/performance-benchmarks.mddocs/cdk/performance-benchmarks.md renamed to docs/cdk/specification/performance-benchmarks.md docs/cdk/performance-benchmarks.md renamed to docs/cdk/specification/performance-benchmarks.md

@@ -3,7 +3,7 @@
 Polygon CDK running in validium mode inherits the core functionalities of zkEVM rollup mode and adds a [data availability layer](dac.md).
 
 !!! danger
-    How can we say that validium inherits from zkEVM rollup when zkEVM rollup is unavailable?
+    How can we say that validium inherits from zkEVM rollup when zkEVM rollup is unavailable? Do we mean non-CDK zkEVM rollup? We need to say so.
 
 ## Key differences
 

docs/cdk/validium-vs-zkevm.md …s/cdk/specification/validium-vs-zkevm.mddocs/cdk/validium-vs-zkevm.md renamed to docs/cdk/specification/validium-vs-zkevm.md docs/cdk/validium-vs-zkevm.md renamed to docs/cdk/specification/validium-vs-zkevm.md

@@ -55,8 +55,8 @@ nav:
         - Manage policies: cdk/how-to/manage-policies.md
       #- Architecture:
       - Specification:
-        - Validium vs zkEVM: cdk/validium-vs-zkevm.md
-        - Performance benchmarks: cdk/performance-benchmarks.md
+        - Validium vs zkEVM: cdk/specification/validium-vs-zkevm.md
+        - Performance benchmarks: cdk/specification/performance-benchmarks.md
       - Concepts:
         - Data availability: cdk/dac.md
      # - API: