13 October 2013

Business Arising

Earlier this month, the Provincial Synod of the Anglican Church of Southern Africa formally adopted the Anglican Covenant. This might seem like a new development in the life of the Covenant, as the zombie Covenant refuses to die in spite of some clear evidence that it had already been buried. However, it is important to note that the same Synod had adopted the Covenant provisionally back in 2010, when the project still had some life to it.

The full resolution reads:
This Synod

1. Notes the adoption of the Anglican Covenant at the Provincial Synod of 2010;
2. Recommits the Anglican Church of Southern Africa to playing the fullest possible role at the heart of the Anglican Communion, working to promote its unity in diversity and strengthening of bonds of affection, in a life of mutuality and interdependence, shared between autonomous churches, acting each as we are called in our own particular contexts and according to our own ordering, in response to this common gift and calling we have received in our Lord Jesus Christ;
3. Reaffirms its belief that this ordering of shared Communion life may be furthered as set out in the Preamble to the Covenant:
We, as Churches of the Anglican Communion, under the Lordship of Jesus Christ, solemnly covenant together in these following affirmations and commitments. As people of God, drawn from “every nation, tribe, people and language” (Rev 7.9), we do this in order to proclaim more effectively in our different contexts the grace of God revealed in the gospel, to offer God’s love in responding to the needs of the world, to maintain the unity of the Spirit in the bond of peace, and together with all God’s people to attain the full stature of Christ (Eph 4.3,13).
4. Resolves to confirm its adoption of the Anglican Covenant.
The key to understanding the actions of the ACSA lies in the first and last paragraphs of the resolution. Given that it had provisionally adopted the Covenant, the more recent action is thus best understood as nothing more than business arising from the previous meeting of Synod.

The reference to “autonomous churches” in paragraph 2 suggests that the ACSA does not intend its formal adoption of the Covenant to impair its own autonomy, nor does it seem likely that it will use the Covenant to interfere in other churches' autonomy, given the emphasis on diversity and “acting each as we are called according to our particular contexts.” Whether the Covenant will change anything, notwithstanding the ACSA's apparent understanding that it isn't intended to, remains to be seen. But for it to bring about any meaningful change, positive or negative, would require its widespread adoption.

My sense is that the Anglican Communion as a whole is generally moving on from this project, and the ACSA has simply cleaned up a bit of unfinished business

16 March 2013

Calling for more study

Note: there hasn't been much recent activity on this blog because there hasn't been much recent activity with respect to the proposed Anglican Covenant. I have some ideas about other topics I would like to pursue in this space, but it was initially set up to address the Anglican Covenant. I have decided to reserve this blog for that topic until the disposition of the Covenant has been determined. Once that happens, I will look to other topics as the muse strikes. In the meantime, posts to this blog will inevitably be sporadic.

As previously noted, the General Synod of the Anglican Church of Canada, at its 2010 meeting, called for study of the proposed Anglican Covenant, to be supported by the production of three documents: a study guide, a legal analysis and a theological analysis. We received an excellent study guide and an equally excellent legal analysis in short order. Last November we were disappointed to receive a flimsy report from the group that had been asked for the theological analysis. I would make a lame joke about how it ought to have been titled The Dogma Ate My Homework, except there was no theology in it.

Resolution A-137 of the General Synod of 2010, having called for study of the Covenant, then “direct[ed] the Council of General Synod, after this period of consultation and study, to bring a recommendation regarding adoption of The Covenant for the Anglican Communion to the General Synod of 2013.”

Yesterday, at its last meeting before the General Synod to be held in July, the Council of General Synod (CoGS) decided on the resolution that it will present to General Synod. To wit, the resolution will:
Request the conversations in the Anglican Church of Canada about the proposed Covenant for the Anglican Communion continue during the next triennium, and

Request the ACWG to monitor continued developments about the proposed Covenant for the Anglican Communion and report to the spring 2016 meeting of COGS and

Direct COGS to bring a recommendation regarding the adoption of the Covenant to General Synod 2016.
You can see the full discussion toward the end of the CoGS notes for March 15th here.

There are several ways to read this development.

First, and most obviously, CoGS is not doing what it was directed to do by the 2010 General Synod. That is, it is not “bring[ing] a recommendation regarding adoption of The Covenant for the Anglican Communion to the General Synod of 2013.” However, in its defence, it could be argued that it would be premature to do so because the period of consultation and study is incomplete. A few dioceses in Canada have undertaken extensive studies of the proposed Covenant in the last three years, but others have presumably been waiting (in vain, as it turned out) for the theological analysis before undertaking their own study. After all, if you're going to do a study, and you've been told that there will be important background material forthcoming, it makes sense to wait for that material. You can't fault dioceses that have been waiting for the background material for not getting on with the study process. Especially when there's evidence that even CoGS hasn't given the Covenant much study. That said, there are no doubt some dioceses across Canada where there simply isn't a critical mass of interest or energy to study the Covenant document. And now that its future and status are in serious question, interest is waning. It would be nice if some credible body were to make a clear declaration as to whether it's worth flogging the horse any more.

The second way of reading CoGS's motion is to see it as a delaying tactic. Perhaps CoGS is suggesting subliminally that General Synod not take any action just now, anticipating a declaration that the horse is dead. Wait a few years, monitor the situation, and then see if there's anything that needs doing.

The third interpretation is that CoGS is suggesting to the dioceses that haven't yet taken the opportunity to study the proposed Covenant that they do so in the next three years or forever hold their collective peace. Maybe. But the problem is that CoGS is not apparently calling for the theological work that was left undone to be done in the next three years. That being the case, the dioceses will still not be in a position to do a thorough study in the next three years because the necessary background material still won't be available. And energy is definitely waning out in the provinces. We have other things to do than engage in a study process that might (and probably will) prove to be entirely superfluous.

It will be interesting to see what General Synod will do with the resolution in July, and what amendments (if any) are introduced.

In the meantime, we continue to watch for the puff of white smoke above Lambeth Palace that will indicate the burning of the Covenant, and the declaration from the balcony: Non habemus pactum.