Online service platform (OSP) generating and transmitting on behalf of primary entity to third party proposal of the primary entity while maintaining the primary entity anonymous

1. A method including at least:

receiving, by a computer system, relationship instance data of a primary entity relating to previous relationship instances of the primary entity with secondary entities;

identifying, by a computer system, a domain of at least one of the secondary entities from the received data;

accessing, by a computer system, previously stored resource digital rules for the domain;

producing, by the computer system applying the resource digital rules to the relationship instance data, a domain resource regarding the domain;

accessing, by a computer system, a previously stored alignment digital rule for the domain;

determining, by a computer system applying the alignment digital rule to at least one of the relationship instance data and the domain resource, whether or not an alignment condition of the domain is met;

assembling, by a computer system automatically, at least some of previously stored proposal components;

acting to enable, by a computer system, specific ones of the assembled proposal components to be viewable by a third party, the specific proposal components not including an identity of the primary entity;

causing, by a computer system, a proposal notification to be transmitted to a computer of an agency of the domain, the proposal notification indicating how the enabled specific proposal components may be viewed by a user of a computer of the agency, the proposal notification further requesting an affirmation input from a computer of the agency, in which at least one of the assembling, the acting to enable and the causing the proposal notification to be transmitted is performed responsive to determining that the alignment condition is not met;

receiving, by a computer system, an affirmation input from a computer of the agency in response to the transmitted proposal notification; and

effectuating, by a computer system, one or more follow-up notifications.

2. The method of claim 1 , in which:

the relationship instance data includes datasets for the domain, and

the alignment condition is not met if the datasets are more than a threshold number.

3. The method of claim 1 , in which:

the relationship instance data includes datasets for the domain,

the datasets include respective base values, and

the alignment condition is not met if a sum of the respective base values exceeds a threshold number.

4. The method of claim 1 , in which:

the relationship instance data includes at least one date of at least one of the relationship instances,

a due date is determinable by the included date, and

the alignment condition is not met if a report has not been filed with an agency of the domain on behalf of the primary entity by the due date about an aspect of the relationship instances.

5. The method of claim 4 , in which:

the relationship instance data includes datasets for the domain, and

the alignment condition is not met if the datasets are more than a threshold number.

6. The method of claim 4 , in which:

the relationship instance data includes datasets for the domain, and

the alignment condition is not met if the datasets are more than a threshold number.

7. The method of claim 1 , further including:

causing, by a computer system, a permission query to be presented in a User Interface (UI) of a computer of the primary entity that is viewable by a user of the primary entity; and

receiving, by a computer system, a permission input from the computer of the primary entity in response to the permission query, and

in which at least one of the assembling, acting to enable and causing the proposal notification to be transmitted is performed responsive to receiving the permission input.

8. The method of claim 1 , further including:

accessing, by a computer system, a previously stored correction digital rule for the domain;

determining, by a computer system applying the correction digital rule to the relationship instance data, whether or not a correction eligibility condition of the domain is met, and

in which the thus assembling is performed responsive to the correction eligibility condition being met.

9. The method of claim 8 , further including:

storing an updated correction digital rule; and

determining again, by a computer system applying the updated correction digital rule to the relationship instance data responsive to the storing, whether or not the correction eligibility condition is met, and

in which the thus assembling is performed responsive to the correction eligibility condition being met.

10. The method of claim 8 , in which:

the relationship instance data includes at least one date associated with at least one of the relationship instances,

a due date is determined from the alignment digital rule and the included date,

a grace period of the domain is determined from the previously stored correction digital rule, and

the correction eligibility condition is met if the grace period has not elapsed since the due date.

11. The method of claim 8 , in which:

the relationship instance data includes datasets for the domain,

the datasets include respective base values, and

the correction eligibility condition is met if a sum of the respective base values is less than a threshold number.

12. The method of claim 1 , in which:

the assembled proposal components are part of a proposed set, and

the proposed set being for a proposal regarding the primary entity meeting the alignment condition at least in part.

13. The method of claim 1 , further including:

accessing, by a computer system, a previously stored correction digital rule for the domain, and

in which a certain proposal component is thus assembled by applying the previously stored correction digital rule.

14. The method of claim 1 , in which:

the assembled proposal components are part of a proposed set, and

at least one of the proposal components of the proposed set is thus assembled by looking up previously stored proposal components for the domain.

15. The method of claim 14 , further including:

updating, by a computer system, the previously stored proposal components;

assembling again, by a computer system automatically and in response to the updating, another proposed set of at least some of the previously stored proposal components; and

causing, by a computer system, a permission query to be presented in a User Interface (UI) of a computer of a user of the primary entity along with proposal components of the other proposed set.

16. The method of claim 1 , further including:

receiving, by a computer system, primary entity data of the primary entity, the primary data including the identity of the primary entity; and

storing the primary entity data, and

in which the assembled proposal components are part of a proposed set and the proposed set includes the identity of the primary entity.

17. The method of claim 1 , further including:

deriving a relevant number from the relationship instance data or the domain resource, and

in which the assembled proposal components are part of a proposed set and the proposed set includes the relevant number.

18. The method of claim 1 , further including:

causing, by a computer system, at least one of the assembled proposal components to be presented in a User Interface (UI) of a computer of a user of the primary entity.

19. The method of claim 18 , further including:

receiving an electronic signature from the user of the primary entity as one more of the assembled proposal components, and

in which the specific ones of the assembled proposal components that are enabled to be viewable by a third party do not include the received an electronic signature from the user of the primary entity.

20. The method of claim 1 , in which:

the assembled proposal components are assembled in a proposal document.

21. The method of claim 20 , further including:

receiving an electronic signature to the proposal document from the user.

22. The method of claim 1 , in which:

the acting to enable includes preparing a proposal webpage with the specific proposal components, and

the proposal notification provides a link to the proposal webpage.

23. The method of claim 1 , in which:

the acting to enable includes preparing a proposal webpage with the specific proposal components and an indication of a non-shown portion of an identity of the primary entity, and

the proposal notification provides a link to the proposal webpage.

24. The method of claim 1 , in which:

the acting to enable includes preparing a proposal document with the specific proposal components, and

the proposal notification provides a link that leads to opening the proposal document.

25. The method of claim 1 , in which:

the acting to enable includes preparing a proposal document with the specific proposal components and an indication of a non-shown portion of an identity of the primary entity, and

the proposal notification provides a link that leads to opening the proposal document.

26. The method of claim 1 , in which:

the acting to enable includes preparing a proposal document with the specific proposal components, and

the proposal notification includes an email has the proposal document as an attachment.

27. The method of claim 1 , in which:

the specific proposal components further include a promise that the identity of the primary entity will be revealed responsive to the affirmation input being received.

28. The method of claim 1 , in which:

the proposal notification includes a promise that the identity of the primary entity will be revealed responsive to the affirmation input being received.

29. The method of claim 1 , further including:

verifying, by a computer system, the received affirmation input against a validity criterion, and

in which the effectuating is performed automatically responsive to the verifying.

30. The method of claim 1 , in which:

the proposal notification enables a representative of the domain to provide an electronic signature, and

the affirmation input includes the provided electronic signature.

31. The method of claim 1 , in which:

the acting to enable includes preparing a proposal document that includes the specific proposal components,

the proposal notification enables a representative of the domain to affix an electronic signature to the proposal document, and

the affirmation input includes the proposal document with the affixed electronic signature by the representative.

32. The method of claim 1 , in which

the affirmation input includes an electronic signature by a representative of the domain; and

further including:

consulting, by a computer system, a registry of approved domain representatives; and

verifying that the electronic signature is from one of the approved domain representatives, and

in which the effectuating is performed automatically responsive to the verifying.

33. The method of claim 1 , in which:

at least one of the one or more follow-up notifications about the received affirmation input is sent to a computer of the primary entity.

34. The method of claim 1 , in which:

at least one of the one or more follow-up notifications about the identity of the primary entity is sent to a computer of the agency.

35. The method of claim 1 , in which:

at least one of the one or more follow-up notifications is sent concurrently to both a computer of the primary entity and to a computer of the agency.

36. The method of claim 1 , further including:

preparing, by a computer system, a final document that lists the assembled proposal components, the identity of the primary entity, an electronic signature by a user of a computer of the primary entity, an identity of the domain and an electronic signature by a representative of the domain; and

making the final document available to a user of a computer of the primary entity and to a user of a computer of the agency.

37. The method of claim 1 , further including:

receiving, by a computer system and in response to the transmitted proposal notification, a negation input instead of an affirmation input; and

transmitting, by a computer system and in response to the received negation input, a negation notification to a computer of the primary entity.