Introduce Action as a terminology concept and update graph

In order to allow for one to many relationships for both activities and
projects, we introduce the concept of an Action to support the singleton
result that is granted by an authorization.

Signed-off-by: Jeremy Ho <[email protected]>

docs/intro/terminology.md

@@ -44,16 +44,17 @@ This section outlines the definitions and common vocabulary used for representin
 
 | Term | Definition | ??? |
 | --- | --- | --- |
-| Activity | A singular defined and regulated intent of action within an area of intent as defined by a referral agency. An activity may require one or more authorizations, e.g., a housing development project. An activity may be associated with a project. | |
+| Action | A regulated action is a specific defined piece of work that may be bounded by an Area of Intent as defined by a referral agency. | |
+| Activity | A specific task that may be a part of a larger ongoing or routine process. It is defined by a set of one or more regulated actions within an area of intent as defined by a referral agency. An activity may require one or more authorizations. | |
 | Activity Bundling | The act of identifying the set of permits required for a certain activity. | This should be refined, not sure if this should belong here as it's not a formal process but a description of a relationship |
 | Application | A submitted form(s) with the intent to obtain or amend an authorization. | This might be getting muddled with the concept of a project. |
 | Area of Intent | A set of one or more parcels which define the location(s) an activity is to be performed. | |
-| Authorization | The act of granting permission to perform a specific activity in a parcel within the Province of BC. Authorizations may take various forms, including a permit, license, tenure, lease, right-of-way, agreement, grant, statutory right, interest or title. | We might need to expand this definition over time as this is the formal umbrella  term for many things. |
+| Authorization | The act of granting permission to perform a specific action in a parcel within the Province of BC. Authorizations may take various forms, including a permit, license, tenure, lease, right-of-way, agreement, grant, statutory right, interest or title. | We might need to expand this definition over time as this is the formal umbrella  term for many things. |
 | Caseload | Work happening with the LOB to facilitate, capture and maintain a permit. | |
 | Disposition | The final decision or outcome made by a statutory decision maker regarding an application. It essentially indicates what action has been taken with respect to the application, and can be represented by a state. | First attempt at defining - needs review |
 | Parcel | A polygon representation of a designated area, location or jurisdiction. Parcels may have varying degrees of accuracy which may or may not come from surveyor submissions. | Rephrased from LTSA page |
-| Permit | An official document which grants permission to carry out a specific activity, such as land use, in a parcel within the Province of BC. In the context of permitting modernization, it is being used as a term for any type of authorization. | |
-| Project | An optional set of one or more activities as defined by an applicant. | |
+| Permit | An official document which grants permission to carry out a specific action, such as land use, in a parcel within the Province of BC. In the context of permitting modernization, it is being used as a term for any type of authorization. | |
+| Project | A temporary, goal-oriented effort designed to achieve a particular outcome within a defined timeframe and scope. It is defined by a set of one or more regulated actions within an area of intent as defined by a referral agency. A project may require one or more authorizations. | |
 | Submission | The completed output of a single form as answered by an applicant. | Add a note like "Submissions require an adjective declaring their application context"? |
 | Workload | A quantifiable measurement of the number of client-driven applications in the queue. | |
 
@@ -67,10 +68,11 @@ title: Actor-Process Workflow
 %% v11 broke and made all links have arrow heads
 %% Ref: https://github.com/mermaid-js/mermaid/issues/5813
 flowchart TB
-  Activity@{ shape: dbl-circ }
-  Applicant@{ shape: stadium }
+  Action@{ shape: dbl-circ }
   AOI@{ shape: rect, label: "Area of
-    Interest" }
+    Intent" }
+  AP@{ label: "Activity /\nProject"}
+  Applicant@{ shape: stadium }
   DM@{ shape: stadium, label: "Decision
     Maker" }
   Facilitator@{ shape: stadium }
@@ -85,14 +87,16 @@ flowchart TB
     Matter Expert" }
   Submission@{ shape: docs }
 
-  Activity ==>|Within an| AOI
+  Action ==>|Within an| AOI
   AOI ---|Defined by| Parcel
-  Applicant -->|Seeking| Activity
-  Applicant -->|May define a| Project
+  AP -->|Specifies one or more| Action
+  AP -.-|Requires one or more| Application
+  Applicant -->|May define an| AP
   Applicant ==>|Completes an| Application
-  Application -->|Requesting for an| Authorization
+  Application -->|Seeking an| Authorization
   Application ==>|Notifies| RA & DM
-  Authorization ==>|Grants permission for| Activity
+  Authorization ==>|Grants permission for| Action
+  Authorization ---|Bounded by| Parcel
   Authorization -->|May impact| IP
   DM ==> Issues ==> Authorization
   DM <-..->|Communicates with| LG
@@ -101,9 +105,6 @@ flowchart TB
   Facilitator <-.->|Coordinates with| DM
   Facilitator <-.->|Works with| SME
   IP <-..->|Consults with| DM
-  Parcel ---|Constrains an| Authorization
-  Project -->|Specifies one or more| Activity
-  Project -.-|Associated with| Application
   SME -.->|Informs| DM
 
   subgraph Application