Remove non plutus core components

.gitattributes

@@ -1,9 +1,6 @@
 # haskell.nix materialized files
 nix/pkgs/haskell/materialized*/**/*.nix linguist-generated=true
-# linguist gets confused by PIR files, and thinks they make up a lot of our source!
-*.pir linguist-detectable=false
 stubs/plutus-ghc-stub/** linguist-vendored=true
 # Large HTML files inside 'notes' are dominating our repoistory language
 # estimate.
 notes/**/*.html linguist-documentation
-doc/* linguist-documentation

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,13 +7,6 @@ assignees: ''
 
 ---
 
-## Area
-
-[] *Plutus Foundation* Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
-[] *Plutus Application Framework* Related to the Plutus application backend (PAB), emulator, Plutus libraries
-[] *Marlowe* Related to Marlowe
-[] *Other* Any other topic (Playgrounds, etc.)
-
 ## Summary
 
 A clear and specific description of what the bug is.
@@ -39,7 +32,6 @@ A clear and concise description of what you expected to happen.
 ## Screenshots and attachments
 
 - If applicable, add screenshots, config files and/or logs to help explain the problem.
-- If the issue is related to the Plutus Playground, please include a link to a gist that reproduces the issue
 
 ## Additional context
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,13 +7,6 @@ assignees: ''
 
 ---
 
-## Area
-
-[] *Plutus Foundation* Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
-[] *Plutus Application Framework* Related to the Plutus application backend (PAB), emulator, Plutus libraries
-[] *Marlowe* Related to Marlowe
-[] *Other* Any other topic (Playgrounds, etc.)
-
 ## Describe the feature you'd like
 
 A clear and detailed description of what you are suggesting.

.github/workflows/test.yml

@@ -19,4 +19,4 @@ jobs:
     steps:
       - uses: actions/checkout@v2.3.4
       - uses: nixbuild/nix-quick-install-action@v7
-      - run: nix-build -A tests.nixpkgsFmt -A tests.purty -A tests.shellcheck -A tests.stylishHaskell --arg supportedSystems '[ builtins.currentSystem ]' --restrict-eval -I . --allowed-uris 'https://github.com/NixOS/nixpkgs https://github.com/input-output-hk https://github.com/NixOS/nixpkgs-channels' --option trusted-public-keys "hydra.iohk.io:f/Ea+s+dFdN+3Y/G+FDgSq+a5NEWhJGzdjvKNGv0/EQ= iohk.cachix.org-1:DpRUyj7h7V830dp/i6Nti+NEO2/nhblbov/8MW7Rqoo= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=" --option substituters "https://hydra.iohk.io https://iohk.cachix.org https://cache.nixos.org/"
+      - run: nix-build -A tests.nixpkgsFmt -A tests.shellcheck -A tests.stylishHaskell --arg supportedSystems '[ builtins.currentSystem ]' --restrict-eval -I . --allowed-uris 'https://github.com/NixOS/nixpkgs https://github.com/input-output-hk https://github.com/NixOS/nixpkgs-channels' --option trusted-public-keys "hydra.iohk.io:f/Ea+s+dFdN+3Y/G+FDgSq+a5NEWhJGzdjvKNGv0/EQ= iohk.cachix.org-1:DpRUyj7h7V830dp/i6Nti+NEO2/nhblbov/8MW7Rqoo= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=" --option substituters "https://hydra.iohk.io https://iohk.cachix.org https://cache.nixos.org/"

ARCHITECTURE.adoc

@@ -27,79 +27,6 @@ include::plutus-tx/ARCHITECTURE.adoc[]
 
 include::plutus-tx-plugin/ARCHITECTURE.adoc[]
 
-== Ledger
-
-To write actual Plutus contracts we need a model of the ledger that we're
-running on. There are two reasons for this:
-
-- The on-chain code needs to work with the data: validators are given information
-  about the current transaction being validated.
-- The off-chain code needs to produce transactions to submit.
-- We want to write tests that simulate the "full" behaviour of contracts, i.e.
-  across time, in a multi-agent scenario.
-
-include::plutus-ledger/ARCHITECTURE.adoc[]
-
-== Contract modelling
-
-We want to help people write "contracts". When we say that, we mean both:
-
-. A high-level application that exposes a limited API and
-is suitable for running inside something like a wallet smart contract backend.
-. An implementation of a conceptual "contract" (e.g. a crowdfunding contract),
-including both the on-chain code and the eventual contract application.
-
-These packages are geared towards providing the tools to do that, and building
-up examples to ensure that we have adequate functionality.
-
-include::plutus-contract/ARCHITECTURE.adoc[]
-
-include::plutus-use-cases/ARCHITECTURE.adoc[]
-
-== Marlowe
-
-Although conceptually separate from Plutus, a fair amount of Marlowe-related
-code is in the Plutus repository. This is for two different reasons:
-
-. We have an implementation of Marlowe on top of Plutus, which depends on the
-other code in the repository.
-. The Marlowe Playground shares code and deployment infrastructure with the
-Plutus Playground.
-
-include::marlowe/ARCHITECTURE.adoc[]
-
-include::marlowe-symbolic/ARCHITECTURE.adoc[]
-
-include::marlowe-actus/ARCHITECTURE.adoc[]
-
-== Playgrounds
-
-The Plutus/Marlowe Playgrounds are our web-based environment for developing and
-testing basic Plutus and Marlowe contracts. That means they're the main way that
-anyone outside the team has interacted with out product!
-
-include::playground-common/ARCHITECTURE.adoc[]
-
-include::plutus-playground-server/ARCHITECTURE.adoc[]
-
-include::marlowe-playground-server/ARCHITECTURE.adoc[]
-
-include::plutus-playground-client/ARCHITECTURE.adoc[]
-
-include::marlowe-playground-client/ARCHITECTURE.adoc[]
-
-include::playground-common/ARCHITECTURE.adoc[]
-
-include::web-common/ARCHITECTURE.adoc[]
-
-include::deployment/ARCHITECTURE.adoc[]
-
-== Smart Contract Backend
-
-The smart contract backend provides the runtime environment for compiled Plutus contracts. It manages the state of contract instances and brokers messages between them and the nodes, users, and wallets that they interact with.
-
-include::plutus-pab/ARCHITECTURE.adoc[]
-
 == Documentation
 
 include::marlowe/ARCHITECTURE.adoc[]